From: Christoph Hellwig Subject: Re: [PATCH 4/4] xen/blkfront: cope with backend that fail empty BLKIF_OP_WRITE_BARRIER requests Date: Tue, 2 Nov 2010 17:54:34 +0100 Message-ID: <20101102165434.GA19703@lst.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Jeremy Fitzhardinge Cc: Jens Axboe , Christoph Hellwig , Linux Kernel Mailing List , Daniel Stodden , Xen-devel , Jeremy Fitzhardinge List-Id: xen-devel@lists.xenproject.org > 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.