From: Peter Enderborg <peter.enderborg@sony.com>
To: 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>,
Randy Dunlap <rdunlap@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>
Subject: [PATCH v8 0/2] debugfs: Add access restriction option
Date: Thu, 16 Jul 2020 09:15:09 +0200 [thread overview]
Message-ID: <20200716071511.26864-1-peter.enderborg@sony.com> (raw)
In-Reply-To: <20200617133738.6631-1-peter.enderborg@sony.com>
Since debugfs include sensitive information it need to be treated
carefully. But it also has many very useful debug functions for userspace.
With this option we can have same configuration for system with
need of debugfs and a way to turn it off. This gives a extra protection
for exposure on systems where user-space services with system
access are attacked.
v2. Removed MOUNT as part of restrictions. Added API's restrictions as
separate restriction.
v3 Updated Documentation after Randy Dunlap reviews and suggestions.
v4 Removed #ifdefs from inode.c and using internal.h for configuration
and now using BIT() for that. Function is now always on, and are
instead selected by a built in default or command line parameter.
Changed return value on debug_mount
Reported-by: kernel test robot <lkp@intel.com>
Im not sure about that it is right
v5 Added notes to config help suggested by GregKH.
Removed _BIT from names, white-space and tab.
(checkpatch did not complain).
v6 Using ALLOW instead of ACCESS as name on BIT's. Change the fs to
mount to make it clear and easy to understand.
v7 Updated Kconfig.debug with Randy Dunlap corrections.
v8 Spell fixes from Randy and using else-if for command argument
parser.
next prev parent reply other threads:[~2020-07-16 7:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 13:37 [PATCH v3] debugfs: Add access restriction option Peter Enderborg
2020-06-17 14:15 ` Greg Kroah-Hartman
2020-06-17 14:39 ` Enderborg, Peter
2020-06-17 15:10 ` Randy Dunlap
2020-06-22 8:30 ` [PATCH v4 0/2] " Peter Enderborg
2020-06-22 8:30 ` [PATCH 1/2] tracefs: Remove unnecessary debug_fs checks Peter Enderborg
2020-06-22 9:18 ` Greg Kroah-Hartman
2020-06-22 13:47 ` Steven Rostedt
2020-06-22 8:30 ` [PATCH 2/2] debugfs: Add access restriction option Peter Enderborg
2020-07-10 13:06 ` Greg Kroah-Hartman
2020-07-15 8:42 ` [PATCH v5 0/2] " Peter Enderborg
2020-07-15 8:42 ` [PATCH 1/2] tracefs: Remove unnecessary debug_fs checks Peter Enderborg
2020-07-15 8:42 ` [PATCH 2/2] debugfs: Add access restriction option Peter Enderborg
2020-07-15 9:39 ` Greg Kroah-Hartman
2020-07-15 10:03 ` Enderborg, Peter
2020-07-15 10:35 ` Greg Kroah-Hartman
2020-07-15 10:59 ` Enderborg, Peter
2020-07-21 6:47 ` Enderborg, Peter
2020-07-15 15:25 ` [PATCH v6 0/2] " Peter Enderborg
2020-07-15 15:25 ` [PATCH 1/2] tracefs: Remove unnecessary debug_fs checks Peter Enderborg
2020-07-15 15:25 ` [PATCH 2/2] debugfs: Add access restriction option Peter Enderborg
2020-07-16 3:30 ` Randy Dunlap
2020-07-16 4:54 ` [PATCH v7 0/2] " Peter Enderborg
2020-07-16 4:54 ` [PATCH 1/2] tracefs: Remove unnecessary debug_fs checks Peter Enderborg
2020-07-16 4:54 ` [PATCH 2/2] debugfs: Add access restriction option Peter Enderborg
2020-07-16 5:12 ` Randy Dunlap
2020-07-16 7:15 ` Peter Enderborg [this message]
2020-07-16 7:15 ` [PATCH 1/2] tracefs: Remove unnecessary debug_fs checks Peter Enderborg
2020-07-16 7:15 ` [PATCH 2/2] debugfs: Add access restriction option Peter Enderborg
2020-07-16 15:26 ` Randy Dunlap
2020-07-23 15:11 ` [PATCH v8 0/2] " Greg Kroah-Hartman
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=20200716071511.26864-1-peter.enderborg@sony.com \
--to=peter.enderborg@sony.com \
--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=mingo@redhat.com \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.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).