[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250915082249.05be3259@kernel.org>
Date: Mon, 15 Sep 2025 08:22:49 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Lei Yang <leiyang@...hat.com>
Cc: Breno Leitao <leitao@...ian.org>, Andrew Lunn <andrew@...n.ch>, "David
S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo
Abeni <pabeni@...hat.com>, Simon Horman <horms@...nel.org>, "Michael S.
Tsirkin" <mst@...hat.com>, Jason Wang <jasowang@...hat.com>, Xuan Zhuo
<xuanzhuo@...ux.alibaba.com>, Eugenio Pérez
<eperezma@...hat.com>, Andrew Lunn <andrew+netdev@...n.ch>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
virtualization@...ts.linux.dev, kernel-team@...a.com
Subject: Re: [PATCH net-next v2 0/7] net: ethtool: add dedicated GRXRINGS
driver callbacks
On Mon, 15 Sep 2025 18:50:15 +0800 Lei Yang wrote:
> Hi Breno
>
> This series of patches introduced a kernel panic bug. The tests are
> based on the linux-next commit [1]. I tried it a few times and found
> that if I didn't apply the current patch, the issue wouldn't be
> triggered. After applying the current patch, the probability of
> triggering the issue was 3/3.
I really doubt the warning you're reporting is related to this series.
Powered by blists - more mailing lists