From: Junxiao Bi <junxiao.bi@oracle.com>
To: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-block@vger.kernel.org
Cc: paul@paul-moore.com, nathanl@linux.ibm.com, axboe@kernel.dk,
jmorris@namei.org, serge@hallyn.com, konrad.wilk@oracle.com,
joe.jin@oracle.com, junxiao.bi@oracle.com
Subject: [PATCH V4 1/2] debugfs: provide a way for relay user bypass lockdown
Date: Thu, 20 Apr 2023 14:53:30 -0700 [thread overview]
Message-ID: <20230420215331.88326-1-junxiao.bi@oracle.com> (raw)
Relay files in debugfs is used to export information from kernel to
userspace, relay user should tell whether the exported information
is safe to access in lockdown mode or not. The access will be denied
by default.
v4 <- v3:
refactor the code to make code more foolproof.
v3 <- v2:
allow only blktrace trace file instead of relay files
https://lore.kernel.org/all/20230418172656.33583-1-junxiao.bi@oracle.com/
v2 <- v1:
Fix build error when CONFIG_RELAY is not defined.
Reported-by: kernel test robot <lkp@intel.com>
Link: https://lore.kernel.org/oe-kbuild-all/202304121714.6mahd9EW-lkp@intel.com/
Signed-off-by: Junxiao Bi <junxiao.bi@oracle.com>
---
fs/debugfs/file.c | 11 +++++++++++
include/linux/relay.h | 16 ++++++++++++++++
kernel/relay.c | 17 +++++++++++++++++
3 files changed, 44 insertions(+)
diff --git a/fs/debugfs/file.c b/fs/debugfs/file.c
index 1f971c880dde..e12dd8634dc6 100644
--- a/fs/debugfs/file.c
+++ b/fs/debugfs/file.c
@@ -21,6 +21,7 @@
#include <linux/pm_runtime.h>
#include <linux/poll.h>
#include <linux/security.h>
+#include <linux/relay.h>
#include "internal.h"
@@ -142,6 +143,13 @@ EXPORT_SYMBOL_GPL(debugfs_file_put);
* Only permit access to world-readable files when the kernel is locked down.
* We also need to exclude any file that has ways to write or alter it as root
* can bypass the permissions check.
+ * Exception:
+ * Relay files in debugfs are used by kernel to transfer data from kernel to
+ * userspace, these files are with permission 0400, but mmap is supported, so
+ * the access is blocked by default. But there are relay users like blktrace
+ * which will only export none security sensitive info to userspace, so provide
+ * a way for relay user to hook in to tell whether accessing the file in lockdown
+ * mode is safe or not.
*/
static int debugfs_locked_down(struct inode *inode,
struct file *filp,
@@ -154,6 +162,9 @@ static int debugfs_locked_down(struct inode *inode,
!real_fops->mmap)
return 0;
+ if (relay_bypass_lockdown(inode, real_fops))
+ return 0;
+
if (security_locked_down(LOCKDOWN_DEBUGFS))
return -EPERM;
diff --git a/include/linux/relay.h b/include/linux/relay.h
index 72b876dd5cb8..0fd1fb638434 100644
--- a/include/linux/relay.h
+++ b/include/linux/relay.h
@@ -147,6 +147,19 @@ struct rchan_callbacks
* This callback is mandatory.
*/
int (*remove_buf_file)(struct dentry *dentry);
+
+ /*
+ * bypass_lockdown - check whether file can be accessed in lockdown mode.
+ *
+ * Called during file open. It depends on each relay user to tell whether
+ * accessing the file is safe or not in lockdown mode.
+ *
+ * The callback should return "true" if allowing access, "false" if not.
+ *
+ * This callback is optional. If not set, accessing the file will be
+ * denied in lockdown mode.
+ */
+ bool (*bypass_lockdown)(struct inode *inode);
};
/*
@@ -279,8 +292,11 @@ extern const struct file_operations relay_file_operations;
#ifdef CONFIG_RELAY
int relay_prepare_cpu(unsigned int cpu);
+extern bool relay_bypass_lockdown(struct inode *inode,
+ const struct file_operations *fops);
#else
#define relay_prepare_cpu NULL
+#define relay_bypass_lockdown(inode, fops) (false)
#endif
#endif /* _LINUX_RELAY_H */
diff --git a/kernel/relay.c b/kernel/relay.c
index 9aa70ae53d24..d5a76566ef62 100644
--- a/kernel/relay.c
+++ b/kernel/relay.c
@@ -1234,6 +1234,23 @@ static ssize_t relay_file_splice_read(struct file *in,
return ret;
}
+bool relay_bypass_lockdown(struct inode *inode,
+ const struct file_operations *fops)
+{
+ struct rchan_buf *buf;
+
+ /* Not a relay file */
+ if (fops != &relay_file_operations)
+ return false;
+
+ buf = (struct rchan_buf *)inode->i_private;
+ if (!buf->chan->cb->bypass_lockdown)
+ return false;
+
+ return buf->chan->cb->bypass_lockdown(inode);
+}
+EXPORT_SYMBOL_GPL(relay_bypass_lockdown);
+
const struct file_operations relay_file_operations = {
.open = relay_file_open,
.poll = relay_file_poll,
--
2.24.3 (Apple Git-128)
next reply other threads:[~2023-04-20 21:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 21:53 Junxiao Bi [this message]
2023-04-20 21:53 ` [PATCH V4 2/2] blktrace: allow access trace file in lockdown mode Junxiao Bi
2023-04-25 17:55 ` Junxiao Bi
2023-04-25 19:12 ` Jens Axboe
2023-04-26 16:32 ` Junxiao Bi
2023-04-28 21:26 ` Paul Moore
2023-04-28 22:41 ` Junxiao Bi
2023-04-30 21:46 ` Paul Moore
2023-05-09 16:13 ` Junxiao Bi
2023-05-26 16:56 ` Junxiao Bi
2023-05-26 21:37 ` Paul Moore
2023-05-26 22:20 ` Junxiao Bi
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=20230420215331.88326-1-junxiao.bi@oracle.com \
--to=junxiao.bi@oracle.com \
--cc=axboe@kernel.dk \
--cc=jmorris@namei.org \
--cc=joe.jin@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=nathanl@linux.ibm.com \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
/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).