diff options
| author | Shin'ichiro Kawasaki <[email protected]> | 2023-01-31 09:26:44 +0000 |
|---|---|---|
| committer | Christoph Hellwig <[email protected]> | 2023-02-01 15:11:20 +0000 |
| commit | bd97a59da6a866e3dee5d2a2d582ec71dbbc84cd (patch) | |
| tree | 5d86374fc198364b2b9eaa314b6c1eed203236d1 /net/ipv6/tcp_ipv6.c | |
| parent | nvme: clear the request_queue pointers on failure in nvme_alloc_io_tag_set (diff) | |
| download | kernel-bd97a59da6a866e3dee5d2a2d582ec71dbbc84cd.tar.gz kernel-bd97a59da6a866e3dee5d2a2d582ec71dbbc84cd.zip | |
nvme-auth: use workqueue dedicated to authentication
NVMe In-Band authentication uses two kinds of works: chap->auth_work and
ctrl->dhchap_auth_work. The latter work flushes or cancels the former
work. However, the both works are queued to the same workqueue nvme-wq.
It results in the lockdep WARNING as follows:
WARNING: possible recursive locking detected
6.2.0-rc4+ #1 Not tainted
--------------------------------------------
kworker/u16:7/69 is trying to acquire lock:
ffff902d52e65548 ((wq_completion)nvme-wq){+.+.}-{0:0}, at: start_flush_work+0x2c5/0x380
but task is already holding lock:
ffff902d52e65548 ((wq_completion)nvme-wq){+.+.}-{0:0}, at: process_one_work+0x210/0x410
To avoid the WARNING, introduce a new workqueue nvme-auth-wq dedicated
to chap->auth_work.
Reported-by: Daniel Wagner <[email protected]>
Link: https://lore.kernel.org/linux-nvme/[email protected]/
Fixes: f50fff73d620 ("nvme: implement In-Band authentication")
Signed-off-by: Shin'ichiro Kawasaki <[email protected]>
Tested-by: Daniel Wagner <[email protected]>
Reviewed-by: Hannes Reinecke <[email protected]>
Signed-off-by: Christoph Hellwig <[email protected]>
Diffstat (limited to 'net/ipv6/tcp_ipv6.c')
0 files changed, 0 insertions, 0 deletions