From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH] xen block backend driver. Date: Wed, 20 Apr 2011 23:40:16 -0400 Message-ID: <20110421034016.GB11501@infradead.org> References: <1303333543-5915-1-git-send-email-konrad.wilk@oracle.com> <1303333543-5915-2-git-send-email-konrad.wilk@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1303333543-5915-2-git-send-email-konrad.wilk@oracle.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: jaxboe@fusionio.com, xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org, konrad@kernel.org List-Id: xen-devel@lists.xenproject.org > +#define WRITE_BARRIER (REQ_WRITE | REQ_FLUSH | REQ_FUA) Any in case you want to keep usingthis POS out of tree you really need to fix this. REQ_FLUSH | REQ_FUA is not equivalent to the old barrier semantics that the Xen disk protocol exported to the guest. You need to drain the whole queue of outstanding I/Os as some old guest (at least those using reiserfs, e.g. old SLES) rely on it.