nvme-tcp: use bh_lock in data_ready
Sagi Grimberg
maintainerPATCH 1/3 nvme-tcp: use bh_lock in data_ready
data_ready may be invoked from send context or from softirq, so need bh locking for that.
Fixes 3f2304f8c6d6 ("nvme-tcp: add NVMe over TCP host driver")
Signed-off-by Sagi Grimberg <[email protected]>
--- drivers/nvme/host/tcp.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/nvme/host/tcp.c +2 -2
@@ -794,11 +794,11 @@ static void nvme_tcp_data_ready(struct sock *sk) {struct nvme_tcp_queue *queue; -read_lock (&sk->sk_callback_lock); +read_lock_bh (&sk->sk_callback_lock); queue = sk->sk_user_data;if (likely (queue && queue->rd_enabled))queue_work_on (queue->io_cpu, nvme_tcp_wq, &queue->io_work); -read_unlock (&sk->sk_callback_lock); +read_unlock_bh (&sk->sk_callback_lock); }static void nvme_tcp_write_space (struct sock *sk)
Signature · 7 lines
2.20.1 _______________________________________________ linux-nvme mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-nvme
Thanks, applied to nvme-5.8.
_______________________________________________
linux-nvme mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-nvme