This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: [PATCH 4/4] xen/blkfront: cope with backend that fail em

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 4/4] xen/blkfront: cope with backend that fail empty BLKIF_OP_WRITE_BARRIER requests
From: Christoph Hellwig <hch@xxxxxx>
Date: Tue, 2 Nov 2010 17:54:34 +0100
Cc: Jens Axboe <axboe@xxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>, Christoph Hellwig <hch@xxxxxx>, Daniel Stodden <daniel.stodden@xxxxxxxxxx>
Delivery-date: Tue, 02 Nov 2010 09:56:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <a90cc3e15a94274bb22b990be16cd1f62747a0dd.1288714384.git.jeremy.fitzhardinge@xxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <cover.1288714384.git.jeremy.fitzhardinge@xxxxxxxxxx> <a90cc3e15a94274bb22b990be16cd1f62747a0dd.1288714384.git.jeremy.fitzhardinge@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.3.28i
>                                      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

<Prev in Thread] Current Thread [Next in Thread>