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
Subject: [git pull] vfs.git pile 2: several fixes to backport
Date: Tue, 7 May 2019 01:58:42 +0100 [thread overview]
Message-ID: <20190507005842.GG23075@ZenIV.linux.org.uk> (raw)
acct_on() fix for deadlock caught be overlayfs folks,
autofs RCU use-after-free SNAFU (->d_manage() can be called
lockless, so we need to RCU-delay freeing the objects it
looks at) and (hopefully) the end of "do we need freeing this
dentry RCU-delayed" whack-a-mole.
The following changes since commit 79a3aaa7b82e3106be97842dedfd8429248896e6:
Linux 5.1-rc3 (2019-03-31 14:39:29 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git stable-fodder
for you to fetch changes up to ce285c267a003acbf607f3540ff71287f82e5282:
autofs: fix use-after-free in lockless ->d_manage() (2019-04-09 19:18:19 -0400)
----------------------------------------------------------------
Al Viro (3):
acct_on(): don't mess with freeze protection
dcache: sort the freeing-without-RCU-delay mess for good.
autofs: fix use-after-free in lockless ->d_manage()
Documentation/filesystems/porting | 5 +++++
fs/autofs/autofs_i.h | 1 +
fs/autofs/inode.c | 2 +-
fs/dcache.c | 24 +++++++++++++-----------
fs/internal.h | 2 --
fs/nsfs.c | 3 +--
include/linux/dcache.h | 2 +-
include/linux/mount.h | 2 ++
kernel/acct.c | 4 ++--
9 files changed, 26 insertions(+), 19 deletions(-)
next reply other threads:[~2019-05-07 0:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 0:58 Al Viro [this message]
2019-05-07 19:55 ` [git pull] vfs.git pile 2: several fixes to backport 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=20190507005842.GG23075@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 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).