All of lore.kernel.org
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux Security Module list 
	<linux-security-module@vger.kernel.org>,
	Casey Schaufler <casey@schaufler-ca.com>
Subject: [GIT PULL] Smack additional patch for v5.11
Date: Tue, 22 Dec 2020 16:43:25 -0800	[thread overview]
Message-ID: <b73e7af1-25d3-1e68-c810-3858abc489d7@schaufler-ca.com> (raw)
In-Reply-To: b73e7af1-25d3-1e68-c810-3858abc489d7.ref@schaufler-ca.com

Hello Linus

Sorry for the 2nd pull request, but this is a fairly important fix
for the privilege handling of smackfs in the face of io_uring. The
novel use of kernel threads in io_uring invalidated an long standing
assumption regarding the privilege of kernel threads. The fix is
simple and safe. It was provided by Jens Axboe <axboe@kernel.dk>
and has been tested.

--
The following changes since commit 9b0072e2b2b588ad75c94f2c6e6c52c8f4bd2657:

  security/smack: remove unused varible 'rc' (2020-11-16 17:26:31 -0800)

are available in the Git repository at:

  https://github.com/cschaufler/smack-next smack-for-5.11

for you to fetch changes up to 942cb357ae7d9249088e3687ee6a00ed2745a0c7:

  Smack: Handle io_uring kernel thread privileges (2020-12-22 15:34:24 -0800)

----------------------------------------------------------------
Casey Schaufler (1):
      Smack: Handle io_uring kernel thread privileges

 security/smack/smack_access.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)



       reply	other threads:[~2020-12-23  0:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b73e7af1-25d3-1e68-c810-3858abc489d7.ref@schaufler-ca.com>
2020-12-23  0:43 ` Casey Schaufler [this message]
2020-12-24 22:11   ` [GIT PULL] Smack additional patch for v5.11 Linus Torvalds
2020-12-24 22:15   ` pr-tracker-bot

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=b73e7af1-25d3-1e68-c810-3858abc489d7@schaufler-ca.com \
    --to=casey@schaufler-ca.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.