[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250909161625.470d2835@kernel.org>
Date: Tue, 9 Sep 2025 16:16:25 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Breno Leitao <leitao@...ian.org>
Cc: Calvin Owens <calvin@...nvd.org>, Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Shuah Khan
<shuah@...nel.org>, Simon Horman <horms@...nel.org>, david decotigny
<decot@...glers.com>, linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux-kselftest@...r.kernel.org, asantostc@...il.com, efault@....de,
kernel-team@...a.com, stable@...r.kernel.org, jv@...sburgh.net
Subject: Re: [PATCH net v3 1/3] netpoll: fix incorrect refcount handling
causing incorrect cleanup
On Tue, 9 Sep 2025 13:17:27 -0700 Breno Leitao wrote:
> On Mon, Sep 08, 2025 at 06:29:58PM -0700, Jakub Kicinski wrote:
> > On Mon, 8 Sep 2025 13:47:24 -0700 Calvin Owens wrote:
> > > I wonder if there might be a demon lurking in bonding+netpoll that this
> > > was papering over? Not a reason not to fix the leaks IMO, I'm just
> > > curious, I don't want to spend time on it if you already did :)
> >
> > +1, I also feel like it'd be good to have some bonding tests in place
> > when we're removing a hack added specifically for bonding.
>
> Do you prefer to have a separated bonding selftest, or, is it better to
> add some bond operations in the torture selftest?
Normal test is preferable, given the flakiness rate and patch volume
I'm a bit scared of randomized testing as part of CI.
Powered by blists - more mailing lists