From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Bart Van Assche <Bart.VanAssche@sandisk.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"hch@lst.de" <hch@lst.de>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: Block device integrity support
Date: Sat, 3 Jun 2017 06:37:41 -0700 [thread overview]
Message-ID: <17329e00-ab17-0036-d152-4ca1b3cce520@kernel.dk> (raw)
In-Reply-To: <20170603073244.GA23235@infradead.org>
On 06/03/2017 12:32 AM, Christoph Hellwig wrote:
> On Fri, Jun 02, 2017 at 03:52:57PM -0700, Jens Axboe wrote:
>> On 06/02/2017 03:38 PM, Bart Van Assche wrote:
>>> On Fri, 2017-06-02 at 18:24 -0400, Martin K. Petersen wrote:
>>>>> then the output shown below appears in the kernel log. Does anyone know how
>>>>> to fix this? Sorry but I'm not really familiar with the integrity
>>>>> code.
>>>>
>>>> Dmitry posted a fix for this a few weeks ago.
>>>
>>> Ah, that's right. Jens, had you noticed this message:
>>> https://www.spinics.net/lists/fstests/msg06214.html?
>>
>> No, unfortunately not. I'll queue it up for 4.13 and mark it
>> stable for 4.12.
>
> Can we please get it into 4.12-rc?
Yes of course, that's actually what I did. I just got the version
numbers mixed up.
--
Jens Axboe
prev parent reply other threads:[~2017-06-03 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 21:53 Block device integrity support Bart Van Assche
2017-06-02 22:24 ` Jens Axboe
2017-06-02 22:26 ` Martin K. Petersen
2017-06-02 22:24 ` Martin K. Petersen
2017-06-02 22:38 ` Bart Van Assche
2017-06-02 22:52 ` Jens Axboe
2017-06-03 7:32 ` Christoph Hellwig
2017-06-03 13:37 ` 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=17329e00-ab17-0036-d152-4ca1b3cce520@kernel.dk \
--to=axboe@kernel.dk \
--cc=Bart.VanAssche@sandisk.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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