[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 07 Jul 2019 15:03:45 +0100
From: Ben Hutchings <ben@...adent.org.uk>
To: Kirill Smelkov <kirr@...edi.com>, stable@...r.kernel.org
Cc: Sasha Levin <sashal@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Miklos Szeredi <miklos@...redi.hu>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3.16 0/2] Fix FUSE read/write deadlock on stream-like
files
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@...r.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.
Ben.
--
Ben Hutchings
Time is nature's way of making sure that
everything doesn't happen at once.
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists