public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jiří Pinkava" <j-pi@seznam.cz>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: dgilbert@interlog.com, linux-scsi@vger.kernel.org,
	JBottomley@parallels.com
Subject: Re: [PATCH] scsi-sg: pass flag to inhibit setting LUN
Date: Fri, 03 Jan 2014 21:47:29 +0100	[thread overview]
Message-ID: <52C721E1.7020002@seznam.cz> (raw)
In-Reply-To: <yq1ha9kzui9.fsf@sermon.lab.mkp.net>

Dne 3.1.2014 21:21, Martin K. Petersen napsal(a):
>>>>>> "Jiří" == Jiří Pinkava <j-pi@seznam.cz> writes:
> Jiří> This patch implements support for inhibiting setting LUN number
> Jiří> for SCSI custom command send via /dev/sgX with ioctl(.., SG_IO,
> Jiří> ...) call.
>
> Is it an absolute requirement that this is a per-command option or could
> we have a scsi_device quirk flag so we didn't have to plumb this through
> the entire I/O stack?
>
It should be enough to limit it to open file descriptor or sg subsystem.

This magic is expected to happen every time device is accessed
trough sg subsystem, but not if it is accessed other way
(eg. it is still some kind of common disk).

My understanding is that sg subsystem allows generic access to device,
in extreme case I might want to send command to LUN which is not the
active one.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2014-01-03 21:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02 13:19 [PATCH] scsi-sg: pass flag to inhibit setting LUN Jiří Pinkava
2014-01-03 20:10 ` Douglas Gilbert
2014-01-06 14:09   ` Jiří Pinkava
2014-01-19 15:56   ` Douglas Gilbert
2014-01-20  3:23     ` James Bottomley
2014-01-03 20:21 ` Martin K. Petersen
2014-01-03 20:47   ` Jiří Pinkava [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=52C721E1.7020002@seznam.cz \
    --to=j-pi@seznam.cz \
    --cc=JBottomley@parallels.com \
    --cc=dgilbert@interlog.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox