diff options
| author | Ming Lei <ming.lei@redhat.com> | 2019-07-24 06:48:40 +0300 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2019-08-05 06:41:29 +0300 |
| commit | f9934a80f91dba8c7029ba7601459e41ea7770aa (patch) | |
| tree | 46a0aff51a0f51bf585ab59302ad06bc6cda9097 /crypto/twofish_generic.c | |
| parent | aa306ab703e9452b1e25cc8e8f04b8df523d0bb8 (diff) | |
| download | linux-f9934a80f91dba8c7029ba7601459e41ea7770aa.tar.xz | |
blk-mq: introduce blk_mq_tagset_wait_completed_request()
blk-mq may schedule to call queue's complete function on remote CPU via
IPI, but doesn't provide any way to synchronize the request's complete
fn. The current queue freeze interface can't provide the synchonization
because aborted requests stay at blk-mq queues during EH.
In some driver's EH(such as NVMe), hardware queue's resource may be freed &
re-allocated. If the completed request's complete fn is run finally after the
hardware queue's resource is released, kernel crash will be triggered.
Prepare for fixing this kind of issue by introducing
blk_mq_tagset_wait_completed_request().
Cc: Max Gurtovoy <maxg@mellanox.com>
Cc: Sagi Grimberg <sagi@grimberg.me>
Cc: Keith Busch <keith.busch@intel.com>
Cc: Christoph Hellwig <hch@lst.de>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Ming Lei <ming.lei@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'crypto/twofish_generic.c')
0 files changed, 0 insertions, 0 deletions