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: 
 <171317343035.4489.13927722462831378141.git-patchwork-notify@kernel.org>
Date: Mon, 15 Apr 2024 09:30:30 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
 pabeni@...hat.com, linux@...ck-us.net, o.rempel@...gutronix.de
Subject: Re: [PATCH net-next] net: dev_addr_lists: move locking out of init/exit
 in kunit

Hello:

This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@...emloft.net>:

On Thu, 11 Apr 2024 11:32:22 -0700 you wrote:
> We lock and unlock rtnl in init/exit for convenience,
> but it started causing problems if the exit is handled
> by a different thread. To avoid having to futz with
> disabling locking assertions move the locking into
> the test cases. We don't use ASSERTs so it should
> be safe.
> 
> [...]

Here is the summary with links:
  - [net-next] net: dev_addr_lists: move locking out of init/exit in kunit
    https://git.kernel.org/netdev/net-next/c/3db3b62955cd

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ