From: Randy Dunlap <rdunlap@infradead.org>
To: Peter Enderborg <peter.enderborg@sony.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
"Rafael J . Wysocki" <rafael@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] debugfs: Add access restriction option
Date: Thu, 11 Jun 2020 08:26:26 -0700 [thread overview]
Message-ID: <91856f40-c44f-6600-b933-f994143c6934@infradead.org> (raw)
In-Reply-To: <20200611152155.2194-1-peter.enderborg@sony.com>
Hi,
Please fix typos:
On 6/11/20 8:21 AM, Peter Enderborg wrote:
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 4379c6ac3265..b1c1446aa90d 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -827,6 +827,17 @@
> useful to also enable the page_owner functionality.
> on: enable the feature
>
> + debugfs= [KNL] When CONFIG_DEBUG_FS_RESTRICTED is set, this parameter
> + enable what is exposed to userspace.
enables
> + Format: { on, no_fs, off }
> + on: All functions are enabled.
> + no_fs: Filesystem is not registered but kernel clients can
> + access apis and a crashkernel can be used to read
APIs
> + it's content. There is noting to mount.
its nothing
> + off: (default) Filesystem is not registered and clients
> + get a -EPERM as result when trying to register files
> + or directory’s within debugfs.
or directories
> +
> debugpat [X86] Enable PAT debugging
>
> decnet.addr= [HW,NET]
thanks.
--
~Randy
prev parent reply other threads:[~2020-06-11 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 15:21 [PATCH v2] debugfs: Add access restriction option Peter Enderborg
2020-06-11 15:26 ` Randy Dunlap [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=91856f40-c44f-6600-b933-f994143c6934@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.enderborg@sony.com \
--cc=rafael@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).