stgt.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ronnie Sahlberg <ronniesahlberg@gmail.com>
To: stgt@vger.kernel.org
Cc: tomof@acm.org
Subject: [Patch 0/0] Fix two issues with WRITE_SAME*
Date: Sun,  2 Oct 2016 09:04:00 -0700	[thread overview]
Message-ID: <1475424242-18168-1-git-send-email-ronniesahlberg@gmail.com> (raw)

Fix two issues with WRITE_SAME* found using the libiscsi test suite.
When TL is set to 0 this means that the command will cover all blocks
from the specified LBA until end of device.
If DataOut is provided then it must be exactly one block in size.
(DataOut may be omitted for unmap operations)

 sbc.c |   18 +++++++++++++++---
 1 file changed, 15 insertions(+), 3 deletions(-)

             reply	other threads:[~2016-10-02 16:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-02 16:04 Ronnie Sahlberg [this message]
2016-10-02 16:04 ` [PATCH 1/2] Validate the DataOut length in WRITE_SAME_1* Ronnie Sahlberg
2016-10-04 21:49   ` FUJITA Tomonori
2016-10-02 16:04 ` [PATCH 2/2] WRITE_SAME_* TL==0 means all blocks from LBA until the end of device Ronnie Sahlberg

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=1475424242-18168-1-git-send-email-ronniesahlberg@gmail.com \
    --to=ronniesahlberg@gmail.com \
    --cc=stgt@vger.kernel.org \
    --cc=tomof@acm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).