All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	stable@vger.kernel.org,
	syzbot+a78926bdac2adb52dc0e@syzkaller.appspotmail.com,
	axboe@kernel.dk, io-uring@vger.kernel.org,
	asml.silence@gmail.com
Subject: Re: [PATCH net] net: expect instance lock in netdev_queue_get_dma_dev()
Date: Mon, 10 Aug 2026 23:20:13 +0000	[thread overview]
Message-ID: <178640401364.250217.82789217556428963.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260806225627.3998672-1-kuba@kernel.org>

Hello:

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

On Thu,  6 Aug 2026 15:56:26 -0700 you wrote:
> netdev_queue_get_dma_dev() uses "compat" locking assert which wants
> either the rtnl_lock or netdev instance lock. This is not right,
> the callers are taking the instance lock unconditionally. All entry
> points for queue config are purely instance locked.
> 
> In other words the callers use netdev_get_by_index_lock(), not
> netdev_get_by_index_lock_ops_compat(). All the state we will
> access is effectively instance lock protected (it's const for
> devices which are not ops-locked).
> 
> [...]

Here is the summary with links:
  - [net] net: expect instance lock in netdev_queue_get_dma_dev()
    https://git.kernel.org/netdev/net/c/92465f46f3c3

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-08-10 23:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 22:56 [PATCH net] net: expect instance lock in netdev_queue_get_dma_dev() Jakub Kicinski
2026-08-10 10:23 ` Simon Horman
2026-08-10 10:27 ` Daniel Borkmann
2026-08-10 23: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=178640401364.250217.82789217556428963.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=io-uring@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+a78926bdac2adb52dc0e@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.