linux-ext4 - Re: [PATCH v4] ext4: fix direct I/O read error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 6 Aug 2020 09:52:42 +0800
From:   姜迎 <jiangying8582@....com>
To:     Sasha Levin <sashal@...nel.org>
Cc:     Jan Kara <jack@...e.cz>, stable@...r.kernel.org, tytso@....edu,
        adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org,
        linux-kernel@...r.kernel.org, wanglong19@...tuan.com,
        heguanjun@...tuan.com
Subject: Re: [PATCH v4] ext4: fix direct I/O read error

Sorry，I will fix this error on 4.4 and 4.9，and then send a patch for 4.4 and 4.9，thanks！

发自我的iPhone

> 在 2020年8月6日，上午9:19，Sasha Levin <sashal@...nel.org> 写道：
> 
> 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