From: Jens Axboe <axboe@kernel.dk>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
kmo@daterainc.com
Subject: Re: bio_integrity_verify() bug causing READ verify to be silently skipped
Date: Tue, 21 Jan 2014 20:24:00 -0800 [thread overview]
Message-ID: <20140122042400.GG20347@kernel.dk> (raw)
In-Reply-To: <1390348402.5567.805.camel@haakon3.risingtidesystems.com>
On Tue, Jan 21 2014, Nicholas A. Bellinger wrote:
> On Fri, 2014-01-17 at 16:58 -0500, Martin K. Petersen wrote:
> > >>>>> "nab" == Nicholas A Bellinger <nab@linux-iscsi.org> writes:
> >
> > >> That breaks partial completion, though. I'll take a look at Kent's
> > >> changes...
> >
> > nab> Ping..? Any updates on a proper bugfix for this..?
> >
> > I did put your patch in my queue and have been working on a fix for the
> > partial completion case. The latter requires a bit of massaging that
> > interferes with other pending changes.
> >
> > Given that your patch does address a valid issue I'm OK with Jens
> > putting it in as is. I'll build upon it for my changes.
> >
>
> <nod>
>
> Jens, are you going to pick this one up, or shall I include it in the
> upcoming target-pending/for-next pull request instead..?
>
> Either way, it needs a CC' to stable for >= v3.10.y.
I'll queue it up, thanks.
--
Jens Axboe
prev parent reply other threads:[~2014-01-22 4:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 4:20 bio_integrity_verify() bug causing READ verify to be silently skipped Nicholas A. Bellinger
2013-12-24 8:52 ` Nicholas A. Bellinger
2014-01-03 20:09 ` Martin K. Petersen
2014-01-17 5:20 ` Nicholas A. Bellinger
2014-01-17 21:58 ` Martin K. Petersen
2014-01-21 23:53 ` Nicholas A. Bellinger
2014-01-22 4:24 ` Jens Axboe [this message]
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=20140122042400.GG20347@kernel.dk \
--to=axboe@kernel.dk \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kmo@daterainc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nab@linux-iscsi.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.