Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From:   =?utf-8?B?5aec6L+O?= <jiangying8582@126.com>
Mime-Version: 1.0 (1.0)
Subject: Re: [PATCH v4] ext4: fix direct I/O read error
Date:   Thu, 6 Aug 2020 09:52:42 +0800
Message-Id: <4E76AAD5-D69F-455F-8B70-A46E50E7D60B@126.com>
References: <20200806011909.GD2975990@sasha-vm>
Cc:     Jan Kara <jack@suse.cz>, 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
In-Reply-To: <20200806011909.GD2975990@sasha-vm>
To:     Sasha Levin <sashal@kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Sorry=EF=BC=8CI will fix this error on 4.4 and 4.9=EF=BC=8Cand then send a p=
atch for 4.4 and 4.9=EF=BC=8Cthanks=EF=BC=81

=E5=8F=91=E8=87=AA=E6=88=91=E7=9A=84iPhone

> =E5=9C=A8 2020=E5=B9=B48=E6=9C=886=E6=97=A5=EF=BC=8C=E4=B8=8A=E5=8D=889:19=
=EF=BC=8CSasha Levin <sashal@kernel.org> =E5=86=99=E9=81=93=EF=BC=9A
>=20
> =EF=BB=BFOn 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 thi=
nk
>> it would be worth it to include the fix in stable trees. Thanks.
>=20
> How far back should it go? It breaks the build on 4.9 and 4.4 but the
> fix for the breakage is trivial.
>=20
> 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).
>=20
> --=20
> Thanks,
> Sasha