From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2VuIDx0b2tlQHJlZGhhdC5jb20+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: aconole@redhat.com, echaudro@redhat.com, i.maximets@ovn.org,
bigeasy@linutronix.de, clrkwllms@kernel.org, rostedt@goodmis.org,
pabeni@redhat.com, mhou@redhat.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, horms@kernel.org,
netdev@vger.kernel.org, dev@openvswitch.org,
linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH net] net: openvswitch: Avoid releasing netdev before teardown completes
Date: Fri, 20 Mar 2026 00:30:04 +0000 [thread overview]
Message-ID: <177396660480.1861152.8680277135332409815.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260318155554.1133405-1-toke@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 18 Mar 2026 16:55:51 +0100 you wrote:
> The patch cited in the Fixes tag below changed the teardown code for
> OVS ports to no longer unconditionally take the RTNL. After this change,
> the netdev_destroy() callback can proceed immediately to the call_rcu()
> invocation if the IFF_OVS_DATAPATH flag is already cleared on the
> netdev.
>
> The ovs_netdev_detach_dev() function clears the flag before completing
> the unregistration, and if it gets preempted after clearing the flag (as
> can happen on an -rt kernel), netdev_destroy() can complete and the
> device can be freed before the unregistration completes. This leads to a
> splat like:
>
> [...]
Here is the summary with links:
- [net] net: openvswitch: Avoid releasing netdev before teardown completes
https://git.kernel.org/netdev/net/c/7c770dadfda5
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:[~2026-03-20 0:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 15:55 [PATCH net] net: openvswitch: Avoid releasing netdev before teardown completes Toke Høiland-Jørgensen
2026-03-20 0: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=177396660480.1861152.8680277135332409815.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2VuIDx0b2tlQHJlZGhhdC5jb20+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=aconole@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.org \
--cc=kuba@kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=mhou@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rostedt@goodmis.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