From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [git pull] Dealing with icache races around mkdir and object creation in general
Date: Sun, 12 Aug 2018 23:52:13 +0100 [thread overview]
Message-ID: <20180812225213.GN6515@ZenIV.linux.org.uk> (raw)
* NFS mkdir/open_by_handle race fix
* analogous solution for FUSE, replacing the one currently in mainline
* new primitive to be used when discarding halfway set up inodes on failed
object creation; gives sane warranties re icache lookups not returning
such doomed by still not freed inodes. A bunch of filesystems switched
to that animal.
* Miklos' fix for last cycle regression in iget5_locked(); -stable will need
a slightly different variant, unfortunately.
* misc bits and pieces around things icache-related (in adfs and jfs).
The following changes since commit 877f919e192a09e77962a13d7165783027dee5fd:
proc: add proc_seq_release (2018-06-27 20:44:38 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.mkdir
for you to fetch changes up to c7b15a8657da7f8d11269c7cc3d8beef10d26b43:
jfs: don't bother with make_bad_inode() in ialloc() (2018-08-03 16:03:33 -0400)
----------------------------------------------------------------
Al Viro (11):
nfs_instantiate(): prevent multiple aliases for directory inode
kill d_instantiate_no_diralias()
new primitive: discard_new_inode()
btrfs: switch to discard_new_inode()
ufs: switch to discard_new_inode()
udf: switch to discard_new_inode()
ext2: make sure that partially set up inodes won't be returned by ext2_iget()
jfs: switch to discard_new_inode()
new helper: inode_fake_hash()
adfs: don't put inodes into icache
jfs: don't bother with make_bad_inode() in ialloc()
Miklos Szeredi (1):
vfs: don't evict uninitialized inode
fs/adfs/inode.c | 2 +-
fs/adfs/super.c | 1 +
fs/btrfs/inode.c | 106 ++++++++++++++++++-------------------------------
fs/dcache.c | 29 +-------------
fs/ext2/ialloc.c | 3 +-
fs/ext2/namei.c | 9 ++---
fs/fuse/dir.c | 15 +++++--
fs/hfs/inode.c | 2 +-
fs/inode.c | 53 ++++++++++++++++++++++---
fs/jfs/jfs_imap.c | 8 +---
fs/jfs/jfs_inode.c | 10 ++---
fs/jfs/namei.c | 12 ++----
fs/jfs/super.c | 2 +-
fs/nfs/dir.c | 9 +++--
fs/udf/namei.c | 12 ++----
fs/ufs/ialloc.c | 3 +-
fs/ufs/namei.c | 9 ++---
fs/xfs/xfs_iops.c | 2 +-
include/linux/dcache.h | 1 -
include/linux/fs.h | 17 +++++++-
20 files changed, 146 insertions(+), 159 deletions(-)
reply other threads:[~2018-08-12 22:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180812225213.GN6515@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