diff options
author | Sagi Grimberg <sagi@grimberg.me> | 2022-07-24 10:58:43 +0200 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2022-08-03 01:22:53 +0200 |
commit | 533d2e8b4d5e4c89772a0adce913525fb86cbbee (patch) | |
tree | d8c1ad51b8243fad91e6cd73bfc558c036ecf2a0 /MAINTAINERS | |
parent | nvme: enable generic interface (/dev/ngXnY) for unknown command sets (diff) | |
download | linux-533d2e8b4d5e4c89772a0adce913525fb86cbbee.tar.xz linux-533d2e8b4d5e4c89772a0adce913525fb86cbbee.zip |
nvmet-tcp: fix lockdep complaint on nvmet_tcp_wq flush during queue teardown
We probably need nvmet_tcp_wq to have MEM_RECLAIM as we are
sending/receiving for the socket from works on this workqueue.
Also this eliminates lockdep complaints:
--
[ 6174.010200] workqueue: WQ_MEM_RECLAIM
nvmet-wq:nvmet_tcp_release_queue_work [nvmet_tcp] is flushing
!WQ_MEM_RECLAIM nvmet_tcp_wq:nvmet_tcp_io_work [nvmet_tcp]
[ 6174.010216] WARNING: CPU: 20 PID: 14456 at kernel/workqueue.c:2628
check_flush_dependency+0x110/0x14c
Reported-by: Yi Zhang <yi.zhang@redhat.com>
Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions