From: Yugansh Mittal <mittalyugansh1@gmail.com>
To: paul@paul-moore.com, stephen.smalley.work@gmail.com
Cc: omosnace@redhat.com, selinux@vger.kernel.org,
linux-kernel@vger.kernel.org, mittalyugansh1@gmail.com
Subject: [PATCH 2/2] selinux: make __inode_security_revalidate non-sleeping
Date: Sun, 24 Aug 2025 18:31:06 +0530 [thread overview]
Message-ID: <20250824130106.35366-1-mittalyugansh1@gmail.com> (raw)
Replace the blocking revalidation logic in __inode_security_revalidate()
with a fast, RCU-safe check of the inode security struct.
Previously, the function could invoke inode_doinit_with_dentry() when
may_sleep was true, which might block. With this change we always avoid
sleeping and return -ECHILD if the inode label is invalid, forcing the
caller to retry in a sleepable context.
This ensures that __inode_security_revalidate() can safely run in
non-sleepable contexts while preserving correct retry semantics.
Signed-off-by: Yugansh Mittal <mittalyugansh1@gmail.com>
---
security/selinux/hooks.c | 22 +++++++++-------------
1 file changed, 9 insertions(+), 13 deletions(-)
diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c
index c95a5874b..2bb94794e 100644
--- a/security/selinux/hooks.c
+++ b/security/selinux/hooks.c
@@ -282,19 +282,15 @@ static int __inode_security_revalidate(struct inode *inode,
if (!selinux_initialized())
return 0;
- if (may_sleep)
- might_sleep();
- else
- return -ECHILD;
-
- /*
- * Check to ensure that an inode's SELinux state is valid and try
- * reloading the inode security label if necessary. This will fail if
- * @dentry is NULL and no dentry for this inode can be found; in that
- * case, continue using the old label.
- */
- inode_doinit_with_dentry(inode, dentry);
- return 0;
+ rcu_read_lock();
+ isec = selinux_inode(inode);
+ if (unlikely(!isec || is_label_invalid(isec))) {
+ rcu_read_unlock();
+ return -ECHILD; /* force caller to handle reload elsewhere */
+ }
+ rcu_read_unlock();
+
+ return 0; /* valid and no sleeping done */
}
static struct inode_security_struct *inode_security_novalidate(struct inode *inode)
--
2.43.0
next reply other threads:[~2025-08-24 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 13:01 Yugansh Mittal [this message]
2025-08-25 12:47 ` Stephen Smalley
2025-08-26 17:23 ` [PATCH v2] [V2] selinux: restore sleepable revalidation; keep fast no-sleep check Yugansh Mittal
2025-08-26 20:08 ` Stephen Smalley
2026-08-15 14:23 ` kernel test robot
2026-08-16 18:20 ` kernel test robot
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=20250824130106.35366-1-mittalyugansh1@gmail.com \
--to=mittalyugansh1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.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
all inboxes | Powered by JetHome®