diff options
author | Jiri Kosina <jkosina@suse.cz> | 2012-05-18 13:50:28 +0200 |
---|---|---|
committer | Jiri Kosina <jkosina@suse.cz> | 2012-05-18 15:19:11 +0200 |
commit | bfa10b8c98bb335bc3e401d3ec947d446f04d1aa (patch) | |
tree | 70c1ace62544811e7f4f39f8bab8b85ee9f89017 /kernel/wait.c | |
parent | 070ad7e793dc6ff753ee682ef7790b3373b471f6 (diff) | |
download | linux-stable-bfa10b8c98bb335bc3e401d3ec947d446f04d1aa.tar.gz linux-stable-bfa10b8c98bb335bc3e401d3ec947d446f04d1aa.tar.bz2 linux-stable-bfa10b8c98bb335bc3e401d3ec947d446f04d1aa.zip |
floppy: remove floppy-specific O_EXCL handling
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".
There is actual userspace-observable change in behavior because of this
since commit e525fd89d380c ("block: make blkdev_get/put() handle exclusive
access") -- on kernels containing this commit, mount of /dev/fd0 causes
the fd0 block device be claimed with _EXCL, preventing subsequent
open(/dev/fd0).
Bring things back into shape, i.e. make it possible, analogically to
other block devices, to mount the floppy and open() it afterwards --
remove the floppy-specific handling and let the generic bdev code O_EXCL
handling take over.
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Acked-by: Tejun Heo <tj@kernel.org>
Acked-by: NeilBrown <neilb@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'kernel/wait.c')
0 files changed, 0 insertions, 0 deletions