diff options
| author | ZiyangZhang <[email protected]> | 2022-08-15 10:36:32 +0800 |
|---|---|---|
| committer | Jens Axboe <[email protected]> | 2022-08-16 06:16:19 -0600 |
| commit | bb24174754afc5a7d185ca5406dcfbc608cdf157 (patch) | |
| tree | ae49a805c0965fd248d732bdef13e1d75a619bce | |
| parent | 966120b51a245c9ff5857c5b169310c248e0ae87 (diff) | |
ublk_drv: update comment for __ublk_fail_req()
Since __ublk_rq_task_work always fails requests immediately during
exiting, __ublk_fail_req() is only called from abort context during
exiting. So lock is unnecessary.
Signed-off-by: ZiyangZhang <[email protected]>
Reviewed-by: Ming Lei <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jens Axboe <[email protected]>
| -rw-r--r-- | drivers/block/ublk_drv.c | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/drivers/block/ublk_drv.c b/drivers/block/ublk_drv.c index 17896172b0fe..685a43b7ae6e 100644 --- a/drivers/block/ublk_drv.c +++ b/drivers/block/ublk_drv.c @@ -605,8 +605,9 @@ static void ublk_complete_rq(struct request *req) } /* - * __ublk_fail_req() may be called from abort context or ->ubq_daemon - * context during exiting, so lock is required. + * Since __ublk_rq_task_work always fails requests immediately during + * exiting, __ublk_fail_req() is only called from abort context during + * exiting. So lock is unnecessary. * * Also aborting may not be started yet, keep in mind that one failed * request may be issued by block layer again. |