diff options
| author | NeilBrown <neilb@suse.de> | 2008-11-06 17:28:01 +1100 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2008-11-06 17:28:01 +1100 |
| commit | cb3ac42b8af357fdd9ad838234245b39e5bdb7fe (patch) | |
| tree | f6c354c2ec374fa35fe64902204d212f0ef30bd4 /drivers/md/raid10.c | |
| parent | 45beca08dd8b6d6a65c5ffd730af2eac7a2c7a03 (diff) | |
| download | op-kernel-dev-cb3ac42b8af357fdd9ad838234245b39e5bdb7fe.zip op-kernel-dev-cb3ac42b8af357fdd9ad838234245b39e5bdb7fe.tar.gz | |
md: revert the recent addition of a call to the BLKRRPART ioctl.
It turns out that it is only safe to call blkdev_ioctl when the device
is actually open (as ->bd_disk is set to NULL on last close). And it
is quite possible for do_md_stop to be called when the device is not
open. So discard the call to blkdev_ioctl(BLKRRPART) which was
added in
commit 934d9c23b4c7e31840a895ba4b7e88d6413c81f3
It is just as easy to call this ioctl from userspace when needed (on
mdadm -S) so leave it out of the kernel
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/raid10.c')
0 files changed, 0 insertions, 0 deletions
