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 12 - work.read_write bugfix
Date: Sat, 8 Jul 2017 01:29:34 +0100 [thread overview]
Message-ID: <20170708002933.GK10672@ZenIV.linux.org.uk> (raw)
file_start_write()/file_end_write() got mixed into vfs_iter_write() by
accident; that's a deadlock for all existing callers - they already
do that, some - quite a bit outside. Easily fixed, fortunately
The following changes since commit a4058c5bce8aded1a12a59990e84e481a96fb490:
nfsd: remove nfsd_vfs_read (2017-06-29 17:49:24 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.read_write
for you to fetch changes up to 62473a2d6f513296e896b64ccfd7ceb7b963795e:
move file_{start,end}_write() out of do_iter_write() (2017-07-06 09:15:47 -0400)
----------------------------------------------------------------
Al Viro (1):
move file_{start,end}_write() out of do_iter_write()
fs/read_write.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
reply other threads:[~2017-07-08 0:29 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=20170708002933.GK10672@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
Powered by JetHome