| To: | xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] [PATCH] Fix error message when detaching block devices |
| From: | Stefan Berger <stefanb@xxxxxxxxxx> |
| Date: | 2006年12月15日 23:46:06 -0500 |
| Delivery-date: | 2006年12月15日 20:44:47 -0800 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
An error occurs if the first detach was successful and the 2nd one is not (of course). Return if the 1st detach is successful, try the 2nd one if it was not successful. Throw an error if the 2nd one fails. This should also fix problems I am currently seeing in the xm-test suite. Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxx>
Attachment:
xm-main-fix-block-detach.diff
Description: Text Data
_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] [PATCH] Only label a resource if ACM is enabled , Stefan Berger |
|---|---|
| Next by Date: | Re: [Xen-devel] [PATCH] Improve XendCheckpoint's forkHelper error handling , Brendan Cully |
| Previous by Thread: | [Xen-devel] [PATCH] Only label a resource if ACM is enabled , Stefan Berger |
| Next by Thread: | Re: [Xen-devel] [PATCH] Fix error message when detaching block devices , Ewan Mellor |
| Indexes: | [Date] [Thread] [Top] [All Lists] |