linux-kernel - Re: linux-next regression: IO errors in with ext4 and xen-blkfront

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101022092015.GA18290@infradead.org>
Date:	Fri, 22 Oct 2010 05:20:15 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Jens Axboe <axboe@...nel.dk>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	Andreas Dilger <adilger.kernel@...ger.ca>,
	Theodore Ts'o <tytso@....edu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Xen-devel@...ts.xensource.com" <Xen-devel@...ts.xensource.com>
Subject: Re: linux-next regression: IO errors in with ext4 and xen-blkfront

On Fri, Oct 22, 2010 at 10:57:40AM +0200, Jens Axboe wrote:
> On 2010-10-22 10:56, Christoph Hellwig wrote:
> > 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.
> 
> Certainly, but I meant in the barrier branch for submission. If
> it doesn't do empty flushes to begin with, that should be fixed
> up before being enabled in any case.

Yes, it should have been disabled log ago.  I had a long discussion with
them abnout it when they introduced the even more buggy barriers by
tags mode for .36 but they simply ignored it.

> I'll disable barrier support in xen-blkfront.c for now.

Thanks.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/