Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net-next v2 0/6] net: hold instance lock around NETDEV_DOWN and NETDEV_GOING_DOWN
Date: Tue, 07 Jul 2026 13:40:15 +0000	[thread overview]
Message-ID: <178343161539.1993077.11580513248901815053.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260702224150.3730033-1-sdf@fomichev.me>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Thu,  2 Jul 2026 15:41:44 -0700 you wrote:
> NETDEV_UP and NETDEV_REGISTER already run under the per-device
> instance lock. The teardown side does not. Make it symmetric so
> ops-locked drivers can rely on the lock being held in both
> directions.
> 
> v2:
> - reword NETDEV_UNREGISTER unlocked rationale (Jakub)
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/6] net: hold instance lock around NETDEV_DOWN/GOING_DOWN
    https://git.kernel.org/netdev/net-next/c/5326fefb9fe8
  - [net-next,v2,2/6] net: dsa: hold instance lock on close-on-shutdown paths
    https://git.kernel.org/netdev/net-next/c/cefa18fab29c
  - [net-next,v2,3/6] net: mtk_eth_soc: hold instance lock around DMA-device-swap close
    https://git.kernel.org/netdev/net-next/c/6034bc4febc9
  - [net-next,v2,4/6] net: rtnetlink: take instance lock inside rtnl_configure_link
    https://git.kernel.org/netdev/net-next/c/b8d2262b966a
  - [net-next,v2,5/6] net: require instance lock for NETDEV_DOWN/GOING_DOWN notifiers
    https://git.kernel.org/netdev/net-next/c/f540caaaca8d
  - [net-next,v2,6/6] net: document NETDEV_UNREGISTER unlocked rationale
    https://git.kernel.org/netdev/net-next/c/538d89fd9146

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



      parent reply	other threads:[~2026-07-07 13:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 22:41 [PATCH net-next v2 0/6] net: hold instance lock around NETDEV_DOWN and NETDEV_GOING_DOWN Stanislav Fomichev
2026-07-02 22:41 ` [PATCH net-next v2 1/6] net: hold instance lock around NETDEV_DOWN/GOING_DOWN Stanislav Fomichev
2026-07-02 22:41 ` [PATCH net-next v2 2/6] net: dsa: hold instance lock on close-on-shutdown paths Stanislav Fomichev
2026-07-02 22:41 ` [PATCH net-next v2 3/6] net: mtk_eth_soc: hold instance lock around DMA-device-swap close Stanislav Fomichev
2026-07-02 22:41 ` [PATCH net-next v2 4/6] net: rtnetlink: take instance lock inside rtnl_configure_link Stanislav Fomichev
2026-07-02 22:41 ` [PATCH net-next v2 5/6] net: require instance lock for NETDEV_DOWN/GOING_DOWN notifiers Stanislav Fomichev
2026-07-02 22:41 ` [PATCH net-next v2 6/6] net: document NETDEV_UNREGISTER unlocked rationale Stanislav Fomichev
2026-07-07 13: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=178343161539.1993077.11580513248901815053.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf.kernel@gmail.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