From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, hkallweit1@gmail.com,
netdev@vger.kernel.org, stable@vger.kernel.org,
martin.stolpe@gmail.com
Subject: Re: [PATCH net 1/1] igb: fix deadlock caused by taking RTNL in RPM resume path
Date: Tue, 21 Dec 2021 03:10:10 +0000 [thread overview]
Message-ID: <164005621090.30905.3402677038991667985.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211220201844.2714498-1-anthony.l.nguyen@intel.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 20 Dec 2021 12:18:44 -0800 you wrote:
> From: Heiner Kallweit <hkallweit1@gmail.com>
>
> Recent net core changes caused an issue with few Intel drivers
> (reportedly igb), where taking RTNL in RPM resume path results in a
> deadlock. See [0] for a bug report. I don't think the core changes
> are wrong, but taking RTNL in RPM resume path isn't needed.
> The Intel drivers are the only ones doing this. See [1] for a
> discussion on the issue. Following patch changes the RPM resume path
> to not take RTNL.
>
> [...]
Here is the summary with links:
- [net,1/1] igb: fix deadlock caused by taking RTNL in RPM resume path
https://git.kernel.org/netdev/net/c/ac8c58f5b535
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:[~2021-12-21 3:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 20:18 [PATCH net 1/1] igb: fix deadlock caused by taking RTNL in RPM resume path Tony Nguyen
2021-12-21 3:10 ` 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=164005621090.30905.3402677038991667985.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=martin.stolpe@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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