From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Joel Becker <jlbec@evilplan.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] configfs fixes for 5.3
Date: Fri, 6 Sep 2019 17:56:50 +0200 [thread overview]
Message-ID: <20190906155650.GA32004@infradead.org> (raw)
Hi Linus,
please pull these late configfs fixe from Al that fix pretty nasty
removal vs attribute access races.
The following changes since commit 089cf7f6ecb266b6a4164919a2e69bd2f938374a:
Linux 5.3-rc7 (2019-09-02 09:57:40 -0700)
are available in the Git repository at:
git://git.infradead.org/users/hch/configfs.git tags/configfs-for-5.3
for you to fetch changes up to b0841eefd9693827afb9888235e26ddd098f9cef:
configfs: provide exclusion between IO and removals (2019-09-04 22:33:51 +0200)
----------------------------------------------------------------
configfs fixes for 5.3
- fix removal vs attribute read/write races (Al Viro)
----------------------------------------------------------------
Al Viro (4):
configfs: stash the data we need into configfs_buffer at open time
configfs_register_group() shouldn't be (and isn't) called in rmdirable parts
configfs: new object reprsenting tree fragments
configfs: provide exclusion between IO and removals
fs/configfs/configfs_internal.h | 15 ++-
fs/configfs/dir.c | 137 +++++++++++++++-----
fs/configfs/file.c | 280 ++++++++++++++++++++--------------------
3 files changed, 257 insertions(+), 175 deletions(-)
next reply other threads:[~2019-09-06 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 15:56 Christoph Hellwig [this message]
2019-09-06 20:00 ` [GIT PULL] configfs fixes for 5.3 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=20190906155650.GA32004@infradead.org \
--to=hch@infradead.org \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).