From: Vladislav Bolkhovitin <vst@vlnb.net>
To: Hannes Reinecke <hare@suse.de>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
James Smart <james.smart@emulex.com>,
Andrew Vasquez <andrew.vasquez@qlogic.com>
Subject: Re: Is there any plan to support 64bit lun in mainline?
Date: Tue, 15 Oct 2013 21:11:11 -0700 [thread overview]
Message-ID: <525E11DF.3040004@vlnb.net> (raw)
In-Reply-To: <525CDA2A.2060308@suse.de>
Hannes Reinecke, on 10/14/2013 11:01 PM wrote:
> And HBAs like lpfc or qla2xxx even have a fast command abort built
> into the firmware, where the firmware will not even wait for a
> command abort to hit the wire but rather just disable the exchange
> internally and return.
Doing so is asking for data corruption. Aborts intended to cleanup commands on the
target, so they could not anyhow badly interact with future commands. Otherwise it is
possible that an old WRITE command stuck in some deep corner inside the target, be
bypassed by such pseudo-abort and then got released AFTER its LBAs written by newer
data, hence overwrite new data by old data.
Vlad
prev parent reply other threads:[~2013-10-16 4:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 6:35 Is there any plan to support 64bit lun in mainline? Wangshen (C)
2013-10-14 10:32 ` Hannes Reinecke
2013-10-14 15:29 ` Christoph Hellwig
2013-10-20 16:20 ` Douglas Gilbert
2013-10-14 18:30 ` James Bottomley
2013-10-15 6:01 ` Hannes Reinecke
2013-10-15 14:58 ` James Bottomley
2013-10-16 4:11 ` Vladislav Bolkhovitin [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=525E11DF.3040004@vlnb.net \
--to=vst@vlnb.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=andrew.vasquez@qlogic.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=james.smart@emulex.com \
--cc=linux-scsi@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