[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z0/O1ivIwiVVNRf0@perf>
Date: Wed, 4 Dec 2024 12:39:02 +0900
From: Youngmin Nam <youngmin.nam@...sung.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Neal Cardwell <ncardwell@...gle.com>, Eric Dumazet
<edumazet@...gle.com>, davem@...emloft.net, dsahern@...nel.org,
pabeni@...hat.com, horms@...nel.org, dujeong.lee@...sung.com,
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, Youngmin
Nam <youngmin.nam@...sung.com>
Subject: Re: [PATCH] tcp: check socket state before calling WARN_ON
On Tue, Dec 03, 2024 at 06:18:39PM -0800, Jakub Kicinski wrote:
> On Tue, 3 Dec 2024 10:34:46 -0500 Neal Cardwell wrote:
> > > I have not seen these warnings firing. Neal, have you seen this in the past ?
> >
> > I can't recall seeing these warnings over the past 5 years or so, and
> > (from checking our monitoring) they don't seem to be firing in our
> > fleet recently.
>
> FWIW I see this at Meta on 5.12 kernels, but nothing since.
> Could be that one of our workloads is pinned to 5.12.
> Youngmin, what's the newest kernel you can repro this on?
>
Hi Jakub.
Thank you for taking an interest in this issue.
We've seen this issue since 5.15 kernel.
Now, we can see this on 6.6 kernel which is the newest kernel we are running.
Powered by blists - more mailing lists