From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jun Kamada Subject: Re: [Patch 0/7] pvSCSI driver Date: Wed, 20 Feb 2008 14:09:11 +0900 Message-ID: <20080220134030.237A.EB2C8575@jp.fujitsu.com> References: <20080218190633.E761.EB2C8575@jp.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: James Harper Cc: kama@jp.fujitsu.com, xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hi James-san, Thank you for your comment. On Wed, 20 Feb 2008 14:58:48 +1100 "James Harper" 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 4:*:*:*". Needless to say, expansion of "xm" or "xend" is required in that case. :-) Best regards, ----- Jun Kamada