From: Christoph Hellwig Subject: Re: linux-next regression: IO errors in with ext4 and xen-blkfront Date: Fri, 22 Oct 2010 04:56:24 -0400 Message-ID: <20101022085624.GA5672@infradead.org> References: <4CBF83A0.8090802@goop.org> <4CBF84C9.6050606@goop.org> <4CC148E5.2030605@kernel.dk> <20101022082916.GA14070@infradead.org> <4CC1515E.6080006@kernel.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4CC1515E.6080006@kernel.dk> Sender: linux-kernel-owner@vger.kernel.org To: Jens Axboe Cc: Christoph Hellwig , Jeremy Fitzhardinge , Andreas Dilger , Theodore Ts'o , Linux Kernel Mailing List , "Xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Fri, Oct 22, 2010 at 10:54:54AM +0200, Jens Axboe wrote: > So how about we just disable barriers for Xen atm? I would really really > like to push that branch out as well now, since I'll be travelling for > most of the merge window this time. Yes, that's what removing/commenting out that line does.