From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?w43DsWlnbyBIdWd1ZXQgPGlodWd1ZXRAcmVkaGF0LmNvbT4=?=@ci.codeaurora.org
Cc: irusskikh@marvell.com, kuba@kernel.org, andrew@lunn.ch,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
dbogdanov@marvell.com, mstarovo@pm.me, netdev@vger.kernel.org,
liali@redhat.com
Subject: Re: [PATCH v2 net] atlantic: fix deadlock at aq_nic_stop
Date: Mon, 24 Oct 2022 09:30:15 +0000 [thread overview]
Message-ID: <166660381593.16636.18419272488332420903.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221020075310.15226-1-ihuguet@redhat.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 20 Oct 2022 09:53:10 +0200 you wrote:
> NIC is stopped with rtnl_lock held, and during the stop it cancels the
> 'service_task' work and free irqs.
>
> However, if CONFIG_MACSEC is set, rtnl_lock is acquired both from
> aq_nic_service_task and aq_linkstate_threaded_isr. Then a deadlock
> happens if aq_nic_stop tries to cancel/disable them when they've already
> started their execution.
>
> [...]
Here is the summary with links:
- [v2,net] atlantic: fix deadlock at aq_nic_stop
https://git.kernel.org/netdev/net/c/6960d133f66e
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:[~2022-10-24 9:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 10:34 [PATCH net] atlantic: fix deadlock at aq_nic_stop Íñigo Huguet
2022-10-14 12:13 ` Andrew Lunn
2022-10-14 12:43 ` Íñigo Huguet
2022-10-14 13:35 ` Andrew Lunn
2022-10-14 13:44 ` Íñigo Huguet
2022-10-15 15:09 ` Andrew Lunn
2022-10-17 7:22 ` Íñigo Huguet
2022-10-18 0:27 ` Andrew Lunn
2022-10-18 2:44 ` Jakub Kicinski
2022-10-18 6:15 ` Íñigo Huguet
2022-10-18 15:59 ` Jakub Kicinski
2022-10-19 6:18 ` Íñigo Huguet
2022-10-19 15:39 ` Jakub Kicinski
2022-10-20 7:46 ` Íñigo Huguet
2022-10-18 6:11 ` Íñigo Huguet
2022-10-20 7:53 ` [PATCH v2 " Íñigo Huguet
2022-10-20 8:55 ` Igor Russkikh
2022-10-20 16:17 ` Íñigo Huguet
2022-10-21 19:01 ` Íñigo Huguet
2022-10-24 9:30 ` 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=166660381593.16636.18419272488332420903.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?w43DsWlnbyBIdWd1ZXQgPGlodWd1ZXRAcmVkaGF0LmNvbT4=?=@ci.codeaurora.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dbogdanov@marvell.com \
--cc=edumazet@google.com \
--cc=irusskikh@marvell.com \
--cc=kuba@kernel.org \
--cc=liali@redhat.com \
--cc=mstarovo@pm.me \
--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;
as well as URLs for NNTP newsgroup(s).