linux-kernel - Re: [dm-devel] Re: [PATCH] Implement barrier support for single device DM devices

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: <170fa0d20805161255i31d768ceh3b15c2640f06524b@mail.gmail.com>
Date:	Fri, 16 May 2008 15:55:30 -0400
From:	"Mike Snitzer" <snitzer@...il.com>
To:	"device-mapper development" <dm-devel@...hat.com>, agk@...hat.com,
	"Ric Wheeler" <ric@....com>, "Michael Tokarev" <mjt@....msk.ru>,
	"Andi Kleen" <andi@...stfloor.org>, linux-kernel@...r.kernel.org
Subject: Re: [dm-devel] Re: [PATCH] Implement barrier support for single device DM devices

On Mon, Feb 18, 2008 at 10:45 PM, Alasdair G Kergon <agk@...hat.com> wrote:
> On Mon, Feb 18, 2008 at 08:52:10AM -0500, Ric Wheeler wrote:
>  > I understand that. Most of the time, dm or md devices are composed of
>  > uniform components which will uniformly support (or not) the cache flush
>  > commands used by barriers.
>
>  As a dm developer, it's "almost none of the time" because trivial
>  configurations aren't the ones that require lots of testing effort.
>
>  Let's stop arguing over "most of the time":-)
>
>  As Andi points out, there are certainly enough real-world users of
>  "single linear or crypt target using one physical device" for it to be
>  worth our supporting it.

Hi Alasdair,

Given that you feel supporting barriers on single device DM targets is
a good thing, what is the status of such support (like Andi's patch)
making it upstream?

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