linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Paul Moore <paul@paul-moore.com>
Subject: [git pull] RCU-safe common_lsm_audit()
Date: Sun, 21 Feb 2021 22:41:42 +0000	[thread overview]
Message-ID: <YDLhphz/PfGLTXfx@zeniv-ca.linux.org.uk> (raw)

	Making common_lsm_audit() non-blocking; we don't really need to grab/drop
dentry in there - rcu_read_lock() is enough.  There's a couple of followups
using that to simplify the logics in selinux, but those hadn't soaked in -next
yet, so they'll have to go in next window.

The following changes since commit d36a1dd9f77ae1e72da48f4123ed35627848507d:

  dump_common_audit_data(): fix racy accesses to ->d_name (2021-01-16 15:11:35 -0500)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.audit

for you to fetch changes up to 23d8f5b684fc30126b7708cad38b753eaa078b3e:

  make dump_common_audit_data() safe to be called from RCU pathwalk (2021-01-16 15:12:08 -0500)

----------------------------------------------------------------
Al Viro (2):
      new helper: d_find_alias_rcu()
      make dump_common_audit_data() safe to be called from RCU pathwalk

 fs/dcache.c            | 25 +++++++++++++++++++++++++
 include/linux/dcache.h |  2 ++
 security/lsm_audit.c   |  5 +++--
 3 files changed, 30 insertions(+), 2 deletions(-)

             reply	other threads:[~2021-02-21 22:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-21 22:41 Al Viro [this message]
2021-02-22 21:35 ` [git pull] RCU-safe common_lsm_audit() 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=YDLhphz/PfGLTXfx@zeniv-ca.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --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 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).