From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
gnaaman@drivenets.com,
syzbot+7a2ab2cdc14d134de553@syzkaller.appspotmail.com
Subject: Re: [PATCH net] net: dev_addr_list: handle first address in __hw_addr_add_ex
Date: Thu, 30 Sep 2021 12:40:07 +0000 [thread overview]
Message-ID: <163300560773.27982.1109794630423909883.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210929153224.1290487-1-kuba@kernel.org>
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
prev parent reply other threads:[~2021-09-30 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 15:32 [PATCH net] net: dev_addr_list: handle first address in __hw_addr_add_ex Jakub Kicinski
2021-09-30 12:40 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=163300560773.27982.1109794630423909883.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=gnaaman@drivenets.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+7a2ab2cdc14d134de553@syzkaller.appspotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).