| 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: <1337014188.29436.18.camel@joe2Laptop> Date: Mon, 14 May 2012 09:49:48 -0700 From: Joe Perches <joe@...ches.com> To: Tejun Heo <tj@...nel.org> Cc: Jiri Kosina <jkosina@...e.cz>, Andrew Morton <akpm@...ux-foundation.org>, Jens Axboe <axboe@...nel.dk>, NeilBrown <neilb@...e.de>, linux-kernel@...r.kernel.org Subject: Re: [PATCH] floppy: remove floppy-specific O_EXCL handling On Mon, 2012-05-14 at 09:25 -0700, Tejun Heo wrote: > Hello, > > On Sun, May 13, 2012 at 11:02:07AM +0200, Jiri Kosina wrote: > > Block layer now handles O_EXCL in a generic way for block devices. > > > > The semantics is however different for floppy and all other block devices, > > as floppy driver contains its own O_EXCL handling. > > > > The semantics for all-but-floppy bdevs is "there can be at most one O_EXCL > > open of this file", while for floppy bdev the semantics is "if someone has > > the bdev open with O_EXCL, noone else can open it". > > > > Remove the floppy-specific handling and let the generic bdev code O_EXCL > > handling take over. > > > > Signed-off-by: Jiri Kosina <jkosina@...e.cz> > > Patch looks good to me but why do we want to change this at this > point? Because the hobgoblins of consistency are as fun to hunt as the wumpus? -- 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