All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/4] [SCSI] Blacklist RSOC for Microsoft iSCSI target devices
Date: Fri, 05 Dec 2014 10:59:18 -0600	[thread overview]
Message-ID: <5481E466.3070802@cs.wisc.edu> (raw)
In-Reply-To: <yq1zjb2g7rh.fsf@sermon.lab.mkp.net>

On 12/4/14, 8:17 PM, Martin K. Petersen wrote:
>>>>>> "Mike" == Mike Christie <michaelc@cs.wisc.edu> writes:
>
> Mike> In case other people test this patch, I wanted to warn people that
> Mike> the MS iSCSI target does the same sequence (sends reject PDU then
> Mike> drops the connection on us) for any command it does not
> Mike> support. We end up seeing the same problem for other commands.
>
> Ick. Have you pinged MS about this again recently? Doesn't sound like
> we'd be the only ones tripping over something like this.

I have not. Until the other day in this thread, I thought they fixed it 
in the newer target versions. I just noticed this behavior was the 
general error handling behavior for all unknown commands yesterday when 
testing your patch. Trying to write up an analysis about why they should 
return a ILLEGAL REQUEST and not drop the connection for unsupported 
commands.

  reply	other threads:[~2014-12-05 16:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04  2:18 [PATCH 1/4] [SCSI] Only blacklist WRITE SAME for VMware virtual disks Martin K. Petersen
2014-12-04  2:18 ` [PATCH 2/4] [SCSI] Blacklist RSOC for Microsoft iSCSI target devices Martin K. Petersen
2014-12-05  1:24   ` Mike Christie
2014-12-05  2:17     ` Martin K. Petersen
2014-12-05 16:59       ` Mike Christie [this message]
2014-12-15 13:47   ` Christoph Hellwig
2014-12-04  2:18 ` [PATCH 3/4] [SCSI] sd: Sanity check the optimal I/O size Martin K. Petersen
2014-12-04  2:18 ` [PATCH 4/4] [SCSI] Remove VPD quirk for Seagate drives Martin K. Petersen

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=5481E466.3070802@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.