From: Sasha Levin <sashal@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: stable@vger.kernel.org, tytso@mit.edu, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
wanglong19@meituan.com, heguanjun@meituan.com,
Jiang Ying <jiangying8582@126.com>
Subject: Re: [PATCH v4] ext4: fix direct I/O read error
Date: Wed, 5 Aug 2020 21:19:09 -0400 [thread overview]
Message-ID: <20200806011909.GD2975990@sasha-vm> (raw)
In-Reply-To: <20200805085107.GC4117@quack2.suse.cz>
On Wed, Aug 05, 2020 at 10:51:07AM +0200, Jan Kara wrote:
>Note to stable tree maintainers (summary from the rather long changelog):
>This is a non-upstream patch. It will not go upstream because the problem
>there has been fixed by converting ext4 to use iomap infrastructure.
>However that change is out of scope for stable kernels and this is a
>minimal fix for the problem that has hit real-world applications so I think
>it would be worth it to include the fix in stable trees. Thanks.
How far back should it go? It breaks the build on 4.9 and 4.4 but the
fix for the breakage is trivial.
It does however suggest that this fix wasn't tested on 4.9 or 4.4, so
I'd like to clarify it here before fixing it up (or dropping it).
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-08-06 1:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 7:57 [PATCH v4] ext4: fix direct I/O read error Jiang Ying
2020-08-05 8:51 ` Jan Kara
2020-08-05 14:29 ` Greg KH
2020-08-06 1:19 ` Sasha Levin [this message]
2020-08-06 1:52 ` 姜迎
-- strict thread matches above, loose matches on Subject: below --
2020-08-05 7:40 Jiang Ying
2020-08-14 8:04 ` Christoph Hellwig
2020-08-14 8:38 ` 姜迎
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=20200806011909.GD2975990@sasha-vm \
--to=sashal@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=heguanjun@meituan.com \
--cc=jack@suse.cz \
--cc=jiangying8582@126.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wanglong19@meituan.com \
/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