linux-kernel - Re: [PATCH net] bonding: don't set oif to bond dev when getting NS target destination

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250811201508.508a7e3d@kernel.org>
Date: Mon, 11 Aug 2025 20:15:08 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Hangbin Liu <liuhangbin@...il.com>
Cc: Jay Vosburgh <jv@...sburgh.net>, netdev@...r.kernel.org, Andrew Lunn
 <andrew+netdev@...n.ch>, "David S. Miller" <davem@...emloft.net>, Eric
 Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Nikolay
 Aleksandrov <razor@...ckwall.org>, Simon Horman <horms@...nel.org>, Shuah
 Khan <shuah@...nel.org>, linux-kselftest@...r.kernel.org,
 linux-kernel@...r.kernel.org, David Wilder <wilder@...ibm.com>
Subject: Re: [PATCH net] bonding: don't set oif to bond dev when getting NS
 target destination

On Tue, 12 Aug 2025 02:04:53 +0000 Hangbin Liu wrote:
> On Mon, Aug 11, 2025 at 09:33:28AM -0700, Jakub Kicinski wrote:
> > On Mon, 11 Aug 2025 07:27:19 -0700 Jay Vosburgh wrote:  
> > > 	Generically, I'm wondering if test updates should be separate
> > > patches from the functional changes as a general policy.  
> > 
> > Yes, not sure if we made it a hard requirement, but I think it's our
> > preference. It is the reason why we don't require cover letters for
> > submissions with 2 patches.
> > 
> > Hangbin, please update config for bonding tests, looks like vlans 
> > are not enabled there today.  
> 
> BTW, I'd like to change the bond config to modules. Because we can't unload
> the modules with current config. It that OK for you?

Yes. I'm not sure if any of the bonding tests need to load the modules
explicitly but we'll find out :) In general modules are fine for the CI.