md: avoid spinlock problem in blk_throtl_exit
blk_throtl_exit assumes that ->queue_lock still exists,
so make sure that it does.
To do this, we stop redirecting ->queue_lock to conf->device_lock
and leave it pointing where it is initialised - __queue_lock.
As the blk_plug functions check the ->queue_lock is held, we now
take that spin_lock explicitly around the plug functions. We don't
need the locking, just the warning removal.
This is needed for any kernel with the blk_throtl code, which is
which is 2.6.37 and later.
Cc: stable@kernel.org
Signed-off-by:
NeilBrown <neilb@suse.de>
Showing
- drivers/md/linear.c 0 additions, 1 deletiondrivers/md/linear.c
- drivers/md/multipath.c 0 additions, 1 deletiondrivers/md/multipath.c
- drivers/md/raid0.c 0 additions, 1 deletiondrivers/md/raid0.c
- drivers/md/raid1.c 4 additions, 2 deletionsdrivers/md/raid1.c
- drivers/md/raid10.c 4 additions, 3 deletionsdrivers/md/raid10.c
- drivers/md/raid5.c 0 additions, 1 deletiondrivers/md/raid5.c
Loading
Please register or sign in to comment