linux-kernel - Re: [PATCH V2] lightnvm: pblk fix for 4.13

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <51587202-78AE-49EB-A1D4-25156447E32F@javigon.com>
Date:   Fri, 28 Jul 2017 16:09:37 +0200
From:   Javier González <javier@...igon.com>
To:     Jens Axboe <axboe@...nel.dk>
Cc:     Matias Bjørling <mb@...htnvm.io>,
        linux-block@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2] lightnvm: pblk fix for 4.13

> On 28 Jul 2017, at 16.06, Jens Axboe <axboe@...nel.dk> wrote:
> 
> On 07/28/2017 07:13 AM, Javier González wrote:
>> Hi Jens,
>> 
>> Can you pick up this fix for 4.13? It is a fix to a read corruption in
>> pblk that has been there form the beginning. It is due to a bad bio
>> manipulation in the case that an I/O containing lbas that are invalid,
>> point to data in the host cache and point to data on the device, all
>> three in a single bio.
>> 
>> The patch applies on top of you for-4.13/block and is available too at:
>>  - https://github.com/OpenChannelSSD/linux/tree/pblk.for-4.13
>> 
>> I marked the patch to fix the original pblk commit, but it does not
>> apply anymore on the original 4.12 code. How do we handle these
>> situations? We make a backport when Greg makes 4.12 stable?
> 
> Greg will email you if it doesn't apply, then you can reply back
> with a version that does apply against 4.12.

Makes sense. Thanks for explaining :)

Javier

Download attachment "signature.asc" of type "application/pgp-signature" (802 bytes)