From: Kirill Smelkov <kirr@nexedi.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: <stable@vger.kernel.org>, Sasha Levin <sashal@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Miklos Szeredi <miklos@szeredi.hu>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3.16 0/2] Fix FUSE read/write deadlock on stream-like files
Date: Sun, 07 Jul 2019 18:13:12 +0000 [thread overview]
Message-ID: <20190707181305.GA25031@deco.navytux.spb.ru> (raw)
In-Reply-To: <ef1625b5c6921289e2f87cdbb0101ff6301b2a7d.camel@decadent.org.uk>
On Sun, Jul 07, 2019 at 03:03:45PM +0100, Ben Hutchings wrote:
> On Sun, 2019-06-09 at 15:41 +0000, Kirill Smelkov wrote:
> > Hello stable team,
> >
> > Please consider applying the following 2 patches to Linux-3.16 stable
> > tree. The patches fix regression introduced in 3.14 where both read and
> > write started to run under lock taken, which resulted in FUSE (and many
> > other drivers) deadlocks for cases where stream-like files are used with
> > read and write being run simultaneously.
> >
> > Please see complete problem description in upstream commit 10dce8af3422
> > ("fs: stream_open - opener for stream-like files so that read and write
> > can run simultaneously without deadlock").
> >
> > The actual FUSE fix (upstream commit bbd84f33652f "fuse: Add
> > FOPEN_STREAM to use stream_open()") was merged into 5.2 with `Cc:
> > stable@vger.kernel.org # v3.14+` mark and is already included into 5.1,
> > 5.0 and 4.19 stable trees. However for some reason it is not (yet ?)
> > included into 4.14, 4.9, 4.4, 3.18 and 3.16 trees.
> >
> > The patches fix a real problem into which my FUSE filesystem ran, and
> > which also likely affects OSSPD (full details are in the patches
> > description). Please consider including the fixes into 3.16 (as well as
> > into other stable trees - I'm sending corresponding series separately -
> > - one per tree).
> [...]
>
> I've queued these up for 3.16, thanks.
Thanks a lot.
Kirill
prev parent reply other threads:[~2019-07-07 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 15:41 [PATCH 3.16 0/2] Fix FUSE read/write deadlock on stream-like files Kirill Smelkov
2019-06-09 14:39 ` [PATCH 3.16 2/2] fuse: Add FOPEN_STREAM to use stream_open() Kirill Smelkov
2019-06-09 15:42 ` [PATCH 3.16 1/2] fs: stream_open - opener for stream-like files so that read and write can run simultaneously without deadlock Kirill Smelkov
2019-07-07 14:03 ` [PATCH 3.16 0/2] Fix FUSE read/write deadlock on stream-like files Ben Hutchings
2019-07-07 18:13 ` Kirill Smelkov [this message]
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=20190707181305.GA25031@deco.navytux.spb.ru \
--to=kirr@nexedi.com \
--cc=ben@decadent.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=sashal@kernel.org \
--cc=stable@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).