xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Bob Liu <bob.liu@oracle.com>
To: Juergen Gross <jgross@suse.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	xen-devel@lists.xen.org, paul.durrant@citrix.com,
	jbeulich@suse.com, roger.pau@citrix.com
Subject: Re: [RFC PATCH] xen-block: introduces extra request to pass-through SCSI commands
Date: Wed, 02 Mar 2016 15:57:27 +0800	[thread overview]
Message-ID: <56D69CE7.2010904@oracle.com> (raw)
In-Reply-To: <56D698C7.9060505@suse.com>

Hi Juergen,

On 03/02/2016 03:39 PM, Juergen Gross wrote:
> On 01/03/16 19:08, Ian Jackson wrote:
>> Bob Liu writes ("Re: [RFC PATCH] xen-block: introduces extra request to pass-through SCSI commands"):
>>> One thing I'm still not sure about PVSCSI is do we have the same security issue since LIO can interface to any block device.
>>> E.g when using a partition /dev/sda1 as the PVSCSI-backend, but the PVSCSI-frontend may still send SCSI operates on LUN bases (the whole disk).
>>
>> I don't think you can use pvscsi to passthrough a partition such as
>> /dev/sda1.  Such a thing is not a SCSI command target.
> 
> It might be possible via the fileio target backend. In this case LUN
> based SCSI operations are ignored/refused/emulated by LIO.
> 

Do you know whether pvscsi can work on top of multipath(the device-mapper framework) or LVMs?
Thank you!

Bob

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-03-02  7:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29  3:37 [RFC PATCH] xen-block: introduces extra request to pass-through SCSI commands Bob Liu
2016-02-29  8:12 ` Juergen Gross
2016-02-29 15:05   ` Konrad Rzeszutek Wilk
2016-02-29 15:34     ` Juergen Gross
2016-02-29  9:13 ` Paul Durrant
2016-02-29 14:55   ` Konrad Rzeszutek Wilk
2016-02-29 15:28     ` Paul Durrant
2016-02-29 15:35       ` Roger Pau Monné
2016-02-29 16:48         ` Konrad Rzeszutek Wilk
2016-02-29 16:56           ` Paul Durrant
2016-02-29 16:14 ` Ian Jackson
2016-02-29 16:29   ` Ian Jackson
2016-02-29 23:45     ` Bob Liu
2016-02-29 23:45     ` Bob Liu
2016-03-01 18:08       ` Ian Jackson
2016-03-02  7:39         ` Juergen Gross
2016-03-02  7:57           ` Bob Liu [this message]
2016-03-02 11:40             ` Ian Jackson
2016-03-02 11:46               ` Paul Durrant
2016-03-02 12:00                 ` Juergen Gross
2016-03-02 12:28               ` Bob Liu
2016-03-02 14:44                 ` Ian Jackson
     [not found]                   ` <20160302172257.GC27821@char.us.oracle.com>
2016-03-03 11:54                     ` Paul Durrant
2016-03-03 12:03                       ` Ian Jackson
2016-03-03 12:25                         ` Juergen Gross
2016-03-03 14:07                           ` Konrad Rzeszutek Wilk
2016-03-03 14:19                             ` Paul Durrant

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=56D69CE7.2010904@oracle.com \
    --to=bob.liu@oracle.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=paul.durrant@citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xen.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 NNTP newsgroup(s).