linux-kernel - Re: [Xen-devel] Re: [PATCH] xen block backend driver.

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: <20110422090904.GA29246@infradead.org>
Date:	Fri, 22 Apr 2011 05:09:04 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Daniel Stodden <daniel.stodden@...rix.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	"jaxboe@...ionio.com" <jaxboe@...ionio.com>,
	"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"konrad@...nel.org" <konrad@...nel.org>
Subject: Re: [Xen-devel] Re: [PATCH] xen block backend driver.

On Thu, Apr 21, 2011 at 12:14:37PM -0700, Daniel Stodden wrote:
> > There is a huge userbase of guests out there that does rely on it.
> 
> Which ones? Old blkfront would have make a difference back then when
> barriers used to be an option, but it never actually declared it, right?

Pre-Linux 2.6.37 guests using reiserfs actually relied on the queue
flushing.  This includes a lot of SLES installation which are still
in common use.  There's only two options to make sure they work:

 (1) keep the original barrier semantics and flush the queue
 (2) do not advertize "barrier" support at all, and make sure to submit
   every I/O we get with the FUA bit.

In practice (2) is going to be faster for most real-life workloads.  So
maybe you should just drop the old "barrier" support and just send
requests with the FUA bit set for now, until you have proper flush
and fua support in the protocol.

> Weeeeeelll, I certainly hope it can deal with backends which never got
> to see those headers. :o)

They probably try to handle it, no idea how correct the handling is
in the end.

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