public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Javier González" <jg@lightnvm.io>, mb@lightnvm.io
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Javier González" <javier@javigon.com>
Subject: Re: [PATCH V2] lightnvm: pblk fix for 4.13
Date: Fri, 28 Jul 2017 08:06:52 -0600	[thread overview]
Message-ID: <924b7b4b-78ee-80d8-ed35-7f41b4d60a91@kernel.dk> (raw)
In-Reply-To: <1501247596-23999-1-git-send-email-javier@javigon.com>

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.

Applied for 4.13.

-- 
Jens Axboe

  parent reply	other threads:[~2017-07-28 14:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-28 13:13 [PATCH V2] lightnvm: pblk fix for 4.13 Javier González
2017-07-28 13:13 ` [PATCH] lightnvm: pblk: advance bio according to lba index Javier González
2017-07-28 14:06 ` Jens Axboe [this message]
2017-07-28 14:09   ` [PATCH V2] lightnvm: pblk fix for 4.13 Javier González

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=924b7b4b-78ee-80d8-ed35-7f41b4d60a91@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=javier@javigon.com \
    --cc=jg@lightnvm.io \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mb@lightnvm.io \
    /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