In order to help us track the data length in ingress_msg when using sk_msg redirect. Signed-off-by: Pengcheng Yang <yangpc@xxxxxxxxxx> --- net/ipv4/tcp_diag.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/net/ipv4/tcp_diag.c b/net/ipv4/tcp_diag.c index 01b50fa79189..b22382820a4b 100644 --- a/net/ipv4/tcp_diag.c +++ b/net/ipv4/tcp_diag.c @@ -11,6 +11,7 @@ #include <linux/inet_diag.h> #include <linux/tcp.h> +#include <linux/skmsg.h> #include <net/netlink.h> #include <net/tcp.h> @@ -28,6 +29,7 @@ static void tcp_diag_get_info(struct sock *sk, struct inet_diag_msg *r, r->idiag_rqueue = max_t(int, READ_ONCE(tp->rcv_nxt) - READ_ONCE(tp->copied_seq), 0); + r->idiag_rqueue += sk_msg_queue_len(sk); r->idiag_wqueue = READ_ONCE(tp->write_seq) - tp->snd_una; } if (info) -- 2.38.1
