Commit 942cb357 authored by Casey Schaufler's avatar Casey Schaufler

Smack: Handle io_uring kernel thread privileges

Smack assumes that kernel threads are privileged for smackfs
operations. This was necessary because the credential of the
kernel thread was not related to a user operation. With io_uring
the credential does reflect a user's rights and can be used.
Suggested-by: default avatarJens Axboe <axboe@kernel.dk>
Acked-by: default avatarJens Axboe <axboe@kernel.dk>
Acked-by: default avatarEric W. Biederman <ebiederm@xmission.com>
Signed-off-by: default avatarCasey Schaufler <casey@schaufler-ca.com>
parent 9b0072e2
...@@ -688,9 +688,10 @@ bool smack_privileged_cred(int cap, const struct cred *cred) ...@@ -688,9 +688,10 @@ bool smack_privileged_cred(int cap, const struct cred *cred)
bool smack_privileged(int cap) bool smack_privileged(int cap)
{ {
/* /*
* All kernel tasks are privileged * Kernel threads may not have credentials we can use.
* The io_uring kernel threads do have reliable credentials.
*/ */
if (unlikely(current->flags & PF_KTHREAD)) if ((current->flags & (PF_KTHREAD | PF_IO_WORKER)) == PF_KTHREAD)
return true; return true;
return smack_privileged_cred(cap, current_cred()); return smack_privileged_cred(cap, current_cred());
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment