| 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
| ||
|
Message-ID: <20070528094358.GM25091@agk.fab.redhat.com> Date: Mon, 28 May 2007 10:43:58 +0100 From: Alasdair G Kergon <agk@...hat.com> To: device-mapper development <dm-devel@...hat.com>, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, linux-raid@...r.kernel.org, Jens Axboe <jens.axboe@...cle.com>, David Chinner <dgc@....com>, Phillip Susi <psusi@....rr.com>, Stefan Bader <Stefan.Bader@...ibm.com>, Andreas Dilger <adilger@...sterfs.com>, Tejun Heo <htejun@...il.com> Subject: Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md. On Mon, May 28, 2007 at 11:30:32AM +1000, Neil Brown wrote: > 1/ A BIO_RW_BARRIER request should never fail with -EOPNOTSUP. The device-mapper position has always been that we require > a zero-length BIO_RW_BARRIER (i.e. containing no data to read or write - or emulated, possibly device-specific) before we can provide full barrier support. (Consider multiple active paths - each must see barrier.) Until every device supports barriers -EOPNOTSUP support is required. (Consider reconfiguration of stacks of devices - barrier support is a dynamic block device property that can switch between available and unavailable at any time.) Alasdair -- agk@...hat.com - 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/
Powered by blists - more mailing lists