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]

Date:	Fri, 22 Oct 2010 04:29:16 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Jens Axboe <axboe@...nel.dk>
Cc:	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

In the barriers tree Xen claims to support flushes, but I doesn't.
It never handles REQ_FLUSH requests.  Try commenting out the

	blk_queue_flush(info->rq, info->feature_flush);

call and things should improve.  I still need to hear back from Xen
folks how to actually implement a cache flush - they only implement
a barrier write privilegue which could never implement an empty
cache flush.  Up to current kernels that meant it would implement
barrier writes with content correctly and silently ignore empty barriers
leading to very interesting data integrity bugs.  From 2.6.37 onwards
it simply won't work anymore at all, which is at least consistent
(modulo the bug of actually claiming to support flushes).

--
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/