Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	willemb@google.com, kuniyu@google.com, horms@kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] tap: do not hold RTNL in open(), release() and queue ioctls
Date: Sat, 21 Nov 2026 19:20:06 +0000	[thread overview]
Message-ID: <179528880628.1140982.13826508228871085522.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261119072258.3157902-1-edumazet@kernel.org>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 19 Nov 2026 08:22:54 +0100 you wrote:
> Opening or closing a macvtap/ipvtap char device acquires RTNL, as do
> the TUNSETQUEUE and TUNGETIFF ioctls, although they only manipulate
> the list of queues attached to the device, which is private to tap.
> Hosts starting and stopping many virtual machines thus add contention
> on RTNL for no good reason.
> 
> This series protects the queue list with a per-device mutex, and
> stops taking RTNL in these four paths.
> 
> [...]

Here is the summary with links:
  - [net-next,1/4] tap: detach queues from the NETDEV_UNREGISTER notifier
    https://git.kernel.org/netdev/net-next/c/5a4431ff4fa7
  - [net-next,2/4] tap: add a mutex to protect queue management
    https://git.kernel.org/netdev/net-next/c/c70849e0b16d
  - [net-next,3/4] tap: do not hold RTNL in open(), release() and queue ioctls
    https://git.kernel.org/netdev/net-next/c/ef7b12deec78
  - [net-next,4/4] tap: remove tap_get_tap_dev() and tap_put_tap_dev()
    https://git.kernel.org/netdev/net-next/c/3d5aa58bec4f

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-11-21 19:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19  7:22 [PATCH net-next 0/4] tap: do not hold RTNL in open(), release() and queue ioctls Eric Dumazet
2026-11-19  7:22 ` [PATCH net-next 1/4] tap: detach queues from the NETDEV_UNREGISTER notifier Eric Dumazet
2026-11-19 23:46   ` Willem de Bruijn
2026-11-19  7:22 ` [PATCH net-next 2/4] tap: add a mutex to protect queue management Eric Dumazet
2026-11-19 23:49   ` Willem de Bruijn
2026-11-19  7:22 ` [PATCH net-next 3/4] tap: do not hold RTNL in open(), release() and queue ioctls Eric Dumazet
2026-11-19  7:22 ` [PATCH net-next 4/4] tap: remove tap_get_tap_dev() and tap_put_tap_dev() Eric Dumazet
2026-11-20  0:03   ` Willem de Bruijn
2026-11-21 19:20 ` 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=179528880628.1140982.13826508228871085522.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemb@google.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