public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: <edward.cree@amd.com>
Cc: linux-net-drivers@amd.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, ecree.xilinx@gmail.com,
	netdev@vger.kernel.org, damir.mansurov@oktetlabs.ru,
	ben@decadent.org.uk
Subject: Re: [PATCH net] sfc: fix deadlock in RSS config read
Date: Sun, 25 Jan 2026 21:20:11 +0000	[thread overview]
Message-ID: <176937601110.3588307.13456617616509726491.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260123161634.1215006-1-edward.cree@amd.com>

Hello:

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

On Fri, 23 Jan 2026 16:16:34 +0000 you wrote:
> From: Edward Cree <ecree.xilinx@gmail.com>
> 
> Since cited commit, core locks the net_device's rss_lock when handling
>  ethtool -x command, so driver's implementation should not lock it
>  again.  Remove the latter.
> 
> Fixes: 040cef30b5e6 ("net: ethtool: move get_rxfh callback under the rss_lock")
> Reported-by: Damir Mansurov <damir.mansurov@oktetlabs.ru>
> Closes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126015
> Suggested-by: Ben Hutchings <ben@decadent.org.uk>
> Signed-off-by: Edward Cree <ecree.xilinx@gmail.com>
> 
> [...]

Here is the summary with links:
  - [net] sfc: fix deadlock in RSS config read
    https://git.kernel.org/netdev/net/c/944c614b0a7a

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



      reply	other threads:[~2026-01-25 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23 16:16 [PATCH net] sfc: fix deadlock in RSS config read edward.cree
2026-01-25 21: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=176937601110.3588307.13456617616509726491.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=ben@decadent.org.uk \
    --cc=damir.mansurov@oktetlabs.ru \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=edward.cree@amd.com \
    --cc=kuba@kernel.org \
    --cc=linux-net-drivers@amd.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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