From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf@fomichev.me>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
corbet@lwn.net, andrew+netdev@lunn.ch, kuniyu@amazon.com,
vladimir.oltean@nxp.com, ecree.xilinx@gmail.com, lukma@denx.de,
m-karicheri2@ti.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, cratiu@nvidia.com
Subject: Re: [PATCH net] net: hold instance lock during NETDEV_CHANGE
Date: Mon, 07 Apr 2025 18:40:38 +0000 [thread overview]
Message-ID: <174405123877.1227543.13613718146765643033.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250404161122.3907628-1-sdf@fomichev.me>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 4 Apr 2025 09:11:22 -0700 you wrote:
> Cosmin reports an issue with ipv6_add_dev being called from
> NETDEV_CHANGE notifier:
>
> [ 3455.008776] ? ipv6_add_dev+0x370/0x620
> [ 3455.010097] ipv6_find_idev+0x96/0xe0
> [ 3455.010725] addrconf_add_dev+0x1e/0xa0
> [ 3455.011382] addrconf_init_auto_addrs+0xb0/0x720
> [ 3455.013537] addrconf_notify+0x35f/0x8d0
> [ 3455.014214] notifier_call_chain+0x38/0xf0
> [ 3455.014903] netdev_state_change+0x65/0x90
> [ 3455.015586] linkwatch_do_dev+0x5a/0x70
> [ 3455.016238] rtnl_getlink+0x241/0x3e0
> [ 3455.019046] rtnetlink_rcv_msg+0x177/0x5e0
>
> [...]
Here is the summary with links:
- [net] net: hold instance lock during NETDEV_CHANGE
https://git.kernel.org/netdev/net/c/04efcee6ef8d
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:[~2025-04-07 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 16:11 [PATCH net] net: hold instance lock during NETDEV_CHANGE Stanislav Fomichev
2025-04-07 18: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=174405123877.1227543.13613718146765643033.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukma@denx.de \
--cc=m-karicheri2@ti.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=vladimir.oltean@nxp.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