From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: AlexanderDuyck@gmail.com, netdev@vger.kernel.org,
kuba@kernel.org, kernel-team@meta.com, andrew+netdev@lunn.ch,
pabeni@redhat.com, davem@davemloft.net
Subject: Re: [net PATCH 0/2] Locking fixes for fbnic driver
Date: Thu, 28 Aug 2025 02:00:09 +0000 [thread overview]
Message-ID: <175634640901.908900.44301486574429233.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <175616242563.1963577.7257712519613275567.stgit@ahduyck-xeon-server.home.arpa>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 25 Aug 2025 15:56:00 -0700 you wrote:
> Address a few locking issues that were reported on the fbnic driver.
> Specifically in one case we were seeing locking leaks due to us not
> releasing the locks in certain exception paths. In another case we were
> using phylink_resume outside of a section in which we held the RTNL mutex
> and as a result we were throwing an assert.
>
>
> [...]
Here is the summary with links:
- [net,1/2] fbnic: Fixup rtnl_lock and devl_lock handling related to mailbox code
https://git.kernel.org/netdev/net/c/2ddaa562b465
- [net,2/2] fbnic: Move phylink resume out of service_task and into open/close
https://git.kernel.org/netdev/net/c/6ede14a2c636
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:[~2025-08-28 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 22:56 [net PATCH 0/2] Locking fixes for fbnic driver Alexander Duyck
2025-08-25 22:56 ` [net PATCH 1/2] fbnic: Fixup rtnl_lock and devl_lock handling related to mailbox code Alexander Duyck
2025-08-26 11:46 ` Przemek Kitszel
2025-08-25 22:56 ` [net PATCH 2/2] fbnic: Move phylink resume out of service_task and into open/close Alexander Duyck
2025-08-26 11:49 ` Przemek Kitszel
2025-08-28 2:00 ` 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=175634640901.908900.44301486574429233.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=AlexanderDuyck@gmail.com \
--cc=alexander.duyck@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--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 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.