 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] xenbus_dev_write and failed writes
| To: | xen-devel@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-devel] xenbus_dev_write and failed writes |
| From: | John Levon <levon@xxxxxxxxxxxxxxxxx> |
| Date: | Fri, 2 Mar 2007 16:06:52 +0000 |
| Delivery-date: | Fri, 02 Mar 2007 08:03:02 -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 |
| User-agent: | Mutt/1.5.9i |
In several places after setting u->len we return directly on error. Apart from the partial write case, it seems all of these should be resetting u->len to 0 as happens in the success case? regards john _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] [PATCH] linux/x86-64: allow kernel init memory to be freed, Jan Beulich |
|---|---|
| Next by Date: | Re: [Xen-devel] [PATCH] linux/x86-64: allow kernel init memory to be freed, Keir Fraser |
| Previous by Thread: | [Xen-devel] [PATCH] Remove temporary {kernel, ramdisk} file when VmError occurred, Masaki Kanno |
| Next by Thread: | Re: [Xen-devel] xenbus_dev_write and failed writes, Keir Fraser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
