nvme-tcp: Use protocol specific operations while reading socket

Using socket specific read_sock() calls instead of directly calling
tcp_read_sock() helps lld module registered handlers if any, to be called
from nvme-tcp host.
This patch therefore replaces the tcp_read_sock() with socket specific
prot_ops.

Signed-off-by: Potnuri Bharat Teja <bharat@chelsio.com>
Acked-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Sagi Grimberg <sagi@grimberg.me>

diff --git a/drivers/nvme/host/tcp.c b/drivers/nvme/host/tcp.c
index 2c5df86882cc388ae33ea559a4ecf64ce8015706..53c32f9bba0844b4bc40538b12637e863ed5dfbb 100644 (file)
--- a/drivers/nvme/host/tcp.c
+++ b/drivers/nvme/host/tcp.c
@@ -1018,14 +1018,15 @@ done:
 
 static int nvme_tcp_try_recv(struct nvme_tcp_queue *queue)
 {
-       struct sock *sk = queue->sock->sk;
+       struct socket *sock = queue->sock;
+       struct sock *sk = sock->sk;
        read_descriptor_t rd_desc;
        int consumed;
 
        rd_desc.arg.data = queue;
        rd_desc.count = 1;
        lock_sock(sk);
-       consumed = tcp_read_sock(sk, &rd_desc, nvme_tcp_recv_skb);
+       consumed = sock->ops->read_sock(sk, &rd_desc, nvme_tcp_recv_skb);
        release_sock(sk);
        return consumed;
 }