From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <Bart.VanAssche@sandisk.com>
Cc: "hch\@lst.de" <hch@lst.de>, "axboe\@fb.com" <axboe@fb.com>,
"linux-block\@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: Block device integrity support
Date: Fri, 02 Jun 2017 18:24:34 -0400 [thread overview]
Message-ID: <yq1lgpahvtp.fsf@oracle.com> (raw)
In-Reply-To: <1496440434.1214.23.camel@sandisk.com> (Bart Van Assche's message of "Fri, 2 Jun 2017 21:53:55 +0000")
Bart,
> modprobe scsi_debug delay=0 dif=3 dix=-1 dev_size_mb=16
^^^^^^^^^^^^
Those options don't make much sense.
> 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.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-06-02 22:24 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 [this message]
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
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=yq1lgpahvtp.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Bart.VanAssche@sandisk.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox