All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Kamada <kama@jp.fujitsu.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: kama@jp.fujitsu.com, xen-devel@lists.xensource.com
Subject: Re: [Patch 0/7] pvSCSI driver
Date: Wed, 20 Feb 2008 14:09:11 +0900	[thread overview]
Message-ID: <20080220134030.237A.EB2C8575@jp.fujitsu.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D0131AD91@trantor>

Hi James-san,

Thank you for your comment.

On Wed, 20 Feb 2008 14:58:48 +1100
"James Harper" <james.harper@bendigoit.com.au> wrote:
> I'm now trying to develop a frontend driver for windows, and triggered a
> BUG() on or around line 328 of scsiback.c, because I wasn't setting bus,
> target, and lun in the request. This effectively breaks Dom0 (hotplug
> scripts refused to work thereafter until a reboot), which means a rogue
> DomU can crash Dom0. I think you should implement a more graceful
> failure path.

Yes, I agree on your opinion. 
Some modification or addition may be needed about error handling,
including Reset/Abort SCSI command. We would like to post new version
ASAP.

However, we also would like to get a lot of comments on *current*
version for the enhancement.


> Also, for what reason are the bus, target, and lun required in the
> request? It look like that's a leftover from an earlier version and I
> don't see that it is required now.

The LUN assignment to guest can provide HBA sharing from multiple
guests. We consider that feature is very useful for many usage
scenarios. And also, LUN assignment covers HBA assignment by using
wildcard, for example "xm scsi-attach <domain> 4:*:*:*". Needless to
say, expansion of "xm" or "xend" is required in that case. :-)

Best regards,

-----
Jun Kamada

  reply	other threads:[~2008-02-20  5:09 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18 10:10 [Patch 0/7] pvSCSI driver Jun Kamada
2008-02-18 12:14 ` James Harper
2008-02-19  2:26   ` Jun Kamada
2008-02-19  2:28     ` James Harper
2008-02-20  3:58 ` James Harper
2008-02-20  5:09   ` Jun Kamada [this message]
2008-02-21  2:19 ` James Harper
2008-02-21  3:39   ` James Harper
2008-02-21  4:23     ` Jun Kamada
2008-02-21  5:30       ` James Harper
2008-02-25  1:53         ` Jun Kamada
2008-02-27 11:16 ` Steven Smith
2008-02-28  2:51   ` Jun Kamada
2008-02-28 11:13     ` Steven Smith
2008-02-29  4:47       ` Jun Kamada
2008-03-03 11:38         ` Steven Smith
2008-03-04  7:57           ` Jun Kamada
2008-03-04 13:05             ` Steven Smith
2008-03-05  2:34               ` James Harper
2008-03-05  9:53                 ` Jun Kamada
2008-03-05  9:56                   ` James Harper
2008-03-05 10:00                     ` Jun Kamada
2008-03-06 23:48                       ` Dan Magenheimer
2008-03-07  1:20                         ` Jun Kamada
2008-03-07  2:55                 ` Jun Kamada
2008-03-07  4:31                   ` James Harper
2008-03-14 19:04                     ` James Smart
2008-03-10 12:00                   ` Steven Smith
2008-03-12  6:23                     ` Jun Kamada
2008-03-13 14:30                       ` Steven Smith
2008-03-17  2:33                         ` Jun Kamada
2008-03-17 17:29                           ` Steven Smith
2008-03-14 19:16                       ` James Smart
2008-03-17  2:59                         ` Jun Kamada

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=20080220134030.237A.EB2C8575@jp.fujitsu.com \
    --to=kama@jp.fujitsu.com \
    --cc=james.harper@bendigoit.com.au \
    --cc=xen-devel@lists.xensource.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.