[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3c7d6caf-00eb-d627-902d-a80f145ea4ce@linux.ibm.com>
Date: Fri, 18 Sep 2020 19:35:17 +0530
From: Ritesh Harjani <riteshh@...ux.ibm.com>
To: Sasha Levin <sashal@...nel.org>, "Theodore Ts'o" <tytso@....edu>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
linux-ext4@...r.kernel.org, Jan Kara <jack@...e.cz>
Subject: Re: [PATCH AUTOSEL 5.4 105/330] ext4: make dioread_nolock the default
Hello Sasha,
On 9/18/20 7:27 AM, Sasha Levin wrote:
> From: Theodore Ts'o <tytso@....edu>
>
> [ Upstream commit 244adf6426ee31a83f397b700d964cff12a247d3 ]
>
> This fixes the direct I/O versus writeback race which can reveal stale
> data, and it improves the tail latency of commits on slow devices.
>
> Link: https://lore.kernel.org/r/20200125022254.1101588-1-tytso@mit.edu
> Signed-off-by: Theodore Ts'o <tytso@....edu>
> Signed-off-by: Sasha Levin <sashal@...nel.org>
I see that the subjected patch is being taken into many different stable
trees. I remember there was a fixes patch on top of this[1].
Below thread[1] has more details. Just wanted to point this one out.
Please ignore if already taken.
[1]: https://www.spinics.net/lists/linux-ext4/msg72219.html
-ritesh
Powered by blists - more mailing lists