netdev - Re: [PATCH net] team: replace team lock with rtnl lock

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <e6f681bb-40b6-4393-9e80-883f06e33b7b@I-love.SAKURA.ne.jp>
Date: Sun, 22 Jun 2025 01:27:45 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: Stanislav Fomichev <stfomichev@...il.com>
Cc: Jakub Kicinski <kuba@...nel.org>,
        Network Development <netdev@...r.kernel.org>,
        Jiri Pirko <jiri@...nulli.us>, Andrew Lunn <andrew+netdev@...n.ch>,
        "David S. Miller"
 <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
        Hillf Danton <hdanton@...a.com>,
        Willem de Bruijn <willemdebruijn.kernel@...il.com>
Subject: Re: [PATCH net] team: replace team lock with rtnl lock

On 2025/06/21 8:20, Stanislav Fomichev wrote:
>> Anyway, we can't remove team lock. Too bad.
> 
> I was hoping to see another revision, but just noticed this part. Can
> you share more on why we can't remove the team lock? I can try to
> give it a stab if you're not planning to send a follow up...

I think we can't remove the team lock unless we convert to always use
the rtnl lock. I don't have plan to propose such change. Please send
your approach.