diff options
author | Ming Lei <ming.lei@canonical.com> | 2015-05-06 04:26:27 (GMT) |
---|---|---|
committer | Jens Axboe <axboe@fb.com> | 2015-05-20 15:05:45 (GMT) |
commit | b04a5636a665f5529fdf69ee7e5512156196f31c (patch) | |
tree | 4a75e8a779f2fe0032d67ed15a8a7df9484ce984 /drivers/md/dm-cache-target.c | |
parent | be32417796c2b8a83fe4cbece83bea96ab9e378f (diff) | |
download | linux-b04a5636a665f5529fdf69ee7e5512156196f31c.tar.xz |
block: replace trylock with mutex_lock in blkdev_reread_part()
The only possible problem of using mutex_lock() instead of trylock
is about deadlock.
If there aren't any locks held before calling blkdev_reread_part(),
deadlock can't be caused by this conversion.
If there are locks held before calling blkdev_reread_part(),
and if these locks arn't required in open, close handler and I/O
path, deadlock shouldn't be caused too.
Both user space's ioctl(BLKRRPART) and md_setup_drive() from
init/do_mounts_md.c belongs to the 1st case, so the conversion is safe
for the two cases.
For loop, the previous patches in this pathset has fixed the ABBA lock
dependency, so the conversion is OK.
For nbd, tx_lock is held when calling the function:
- both open and release won't hold the lock
- when blkdev_reread_part() is run, I/O thread has been stopped
already, so tx_lock won't be acquired in I/O path at that time.
- so the conversion won't cause deadlock for nbd
For dasd, both dasd_open(), dasd_release() and request function don't
acquire any mutex/semphone, so the conversion should be safe.
Reviewed-by: Christoph Hellwig <hch@lst.de>
Tested-by: Jarod Wilson <jarod@redhat.com>
Acked-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Ming Lei <ming.lei@canonical.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'drivers/md/dm-cache-target.c')
0 files changed, 0 insertions, 0 deletions