diff options
| author | Ming Lei <ming.lei@redhat.com> | 2019-04-30 04:52:24 +0300 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2019-05-04 16:24:04 +0300 |
| commit | fbc2a15e3433058582e5635aabe48a3011a644a8 (patch) | |
| tree | 0d65a92b4719bfb308bc0b52744296c089a906ef /fs/buffer.c | |
| parent | e87eb301bee183d82bb3d04bd71b6660889a2588 (diff) | |
| download | linux-fbc2a15e3433058582e5635aabe48a3011a644a8.tar.xz | |
blk-mq: move cancel of requeue_work into blk_mq_release
With holding queue's kobject refcount, it is safe for driver
to schedule requeue. However, blk_mq_kick_requeue_list() may
be called after blk_sync_queue() is done because of concurrent
requeue activities, then requeue work may not be completed when
freeing queue, and kernel oops is triggered.
So moving the cancel of requeue_work into blk_mq_release() for
avoiding race between requeue and freeing queue.
Cc: Dongli Zhang <dongli.zhang@oracle.com>
Cc: James Smart <james.smart@broadcom.com>
Cc: Bart Van Assche <bart.vanassche@wdc.com>
Cc: linux-scsi@vger.kernel.org,
Cc: Martin K . Petersen <martin.petersen@oracle.com>,
Cc: Christoph Hellwig <hch@lst.de>,
Cc: James E . J . Bottomley <jejb@linux.vnet.ibm.com>,
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Tested-by: James Smart <james.smart@broadcom.com>
Signed-off-by: Ming Lei <ming.lei@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'fs/buffer.c')
0 files changed, 0 insertions, 0 deletions