[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z4nl0h1IZ5R/KDEc@perf>
Date: Fri, 17 Jan 2025 14:08:34 +0900
From: Youngmin Nam <youngmin.nam@...sung.com>
To: Neal Cardwell <ncardwell@...gle.com>
Cc: Eric Dumazet <edumazet@...gle.com>, Youngmin Nam
<youngmin.nam@...sung.com>, Jakub Kicinski <kuba@...nel.org>,
davem@...emloft.net, dsahern@...nel.org, pabeni@...hat.com,
horms@...nel.org, guo88.liu@...sung.com, yiwang.cai@...sung.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
joonki.min@...sung.com, hajun.sung@...sung.com, d7271.choe@...sung.com,
sw.ju@...sung.com, "Dujeong.lee" <dujeong.lee@...sung.com>
Subject: Re: [PATCH] tcp: check socket state before calling WARN_ON
> Thanks for all the details! If the ramdump becomes available again at
> some point, would it be possible to pull out the following values as
> well:
>
> tp->mss_cache
> inet_csk(sk)->icsk_pmtu_cookie
> inet_csk(sk)->icsk_ca_state
>
> Thanks,
> neal
>
Hi Neal. Happy new year.
We are currently trying to capture a tcpdump during the problem situation
to construct the Packetdrill script. However, this issue does not occur very often.
By the way, we have a full ramdump, so we can provide the information you requested.
tp->packets_out = 0
tp->sacked_out = 0
tp->lost_out = 4
tp->retrans_out = 1
tcp_is_sack(tp) = 1
tp->mss_cache = 1428
inet_csk(sk)->icsk_ca_state = 4
inet_csk(sk)->icsk_pmtu_cookie = 1500
If you need any specific information from the ramdump, please let me know.
Thanks.
Powered by blists - more mailing lists