| 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
| ||
|
Message-Id:
<174240723503.1136881.3874262773936408000.git-patchwork-notify@kernel.org>
Date: Wed, 19 Mar 2025 18:00:35 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Stanislav Fomichev <sdf@...ichev.me>
Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, linux-kernel@...r.kernel.org,
willemdebruijn.kernel@...il.com, jasowang@...hat.com, andrew+netdev@...n.ch,
horms@...nel.org, jdamato@...tly.com, kory.maincent@...tlin.com,
kuniyu@...zon.com, atenart@...nel.org
Subject: Re: [PATCH net-next v2 0/2] net: bring back dev_addr_sem
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@...hat.com>:
On Wed, 12 Mar 2025 12:05:11 -0700 you wrote:
> Kohei reports an issue with dev_addr_sem conversion to netdev instance
> lock in [0]. Based on the discussion, switching to netdev instance
> lock to protect the address might not work for the devices that
> are not using netdev ops lock.
> Bring dev_addr_sem instance lock back but fix the ordering.
>
> 0: https://lore.kernel.org/netdev/20250308203835.60633-2-enjuk@amazon.com
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] Revert "net: replace dev_addr_sem with netdev instance lock"
https://git.kernel.org/netdev/net-next/c/8033d2aef517
- [net-next,v2,2/2] net: reorder dev_addr_sem lock
https://git.kernel.org/netdev/net-next/c/6dd132516f8e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists