From: Christoph Hellwig <hch@infradead.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Sagi Grimberg <sagig@mellanox.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Mike Christie <michaelc@cs.wisc.edu>,
Nicholas Bellinger <nab@linux-iscsi.org>
Subject: Re: Crash on WRITE SAME
Date: Wed, 2 Jul 2014 11:36:07 -0700 [thread overview]
Message-ID: <20140702183607.GA19117@infradead.org> (raw)
In-Reply-To: <alpine.LRH.2.02.1407021423240.20183@file01.intranet.prod.int.rdu2.redhat.com>
On Wed, Jul 02, 2014 at 02:29:05PM -0400, Mikulas Patocka wrote:
> And what about protection information for commands that transfer partial
> sectors? (for example, UMAP transfers 24 bytes). Should
> scsi_transfer_length return 24 or 32 in this case?
As far as I understand so far PI is only defined for READ/WRITE
commands. But I'll defer to Martin who is a much better source for
information on this topic.
next prev parent reply other threads:[~2014-07-02 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 18:05 Crash on WRITE SAME Mikulas Patocka
2014-07-02 18:13 ` Christoph Hellwig
2014-07-02 18:29 ` Mikulas Patocka
2014-07-02 18:36 ` Christoph Hellwig [this message]
2014-07-03 7:33 ` Sagi Grimberg
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=20140702183607.GA19117@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=mpatocka@redhat.com \
--cc=nab@linux-iscsi.org \
--cc=sagig@mellanox.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