netdev - Re: [PATCH net] net: dev_addr_list: handle first address in __hw_addr_add

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: <163300560773.27982.1109794630423909883.git-patchwork-notify@kernel.org>
Date:   Thu, 30 Sep 2021 12:40:07 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     davem@...emloft.net, netdev@...r.kernel.org, gnaaman@...venets.com,
        syzbot+7a2ab2cdc14d134de553@...kaller.appspotmail.com
Subject: Re: [PATCH net] net: dev_addr_list: handle first address in
 __hw_addr_add_ex

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Wed, 29 Sep 2021 08:32:24 -0700 you wrote:
> struct dev_addr_list is used for device addresses, unicast addresses
> and multicast addresses. The first of those needs special handling
> of the main address - netdev->dev_addr points directly the data
> of the entry and drivers write to it freely, so we can't maintain
> it in the rbtree (for now, at least, to be fixed in net-next).
> 
> Current work around sprinkles special handling of the first
> address on the list throughout the code but it missed the case
> where address is being added. First address will not be visible
> during subsequent adds.
> 
> [...]

Here is the summary with links:
  - [net] net: dev_addr_list: handle first address in __hw_addr_add_ex
    https://git.kernel.org/netdev/net/c/a5b8fd657881

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html