 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] Re: [PATCH 4/4] xen/blkfront: cope with backend that fail em
> info->gd->disk_name);
> error = -EOPNOTSUPP;
> + }
> + if (unlikely(bret->status == BLKIF_RSP_ERROR &&
> + info->shadow[id].req.nr_segments == 0)) {
> + printk(KERN_WARNING "blkfront: %s: empty write
> barrier op failed\n",
> + info->gd->disk_name);
> + error = -EOPNOTSUPP;
> + }
We don't use -EOPNOTSUPP anymore in the new world order, anything
barrier related is just a normal I/O error now.
_______________________________________________
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] audit_p2m errors, p2m_mmio_direct turns into p2m_ram_logdirty, Olaf Hering |
|---|---|
| Next by Date: | [Xen-devel] fxsave, fnsave, ltr hang for guest OS., alarson |
| Previous by Thread: | [Xen-devel] [PATCH 4/4] xen/blkfront: cope with backend that fail empty BLKIF_OP_WRITE_BARRIER requests, Jeremy Fitzhardinge |
| Next by Thread: | [Xen-devel] audit_p2m errors, p2m_mmio_direct turns into p2m_ram_logdirty, Olaf Hering |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
