From: patchwork-bot+netdevbpf@kernel.org
To: Sicong Huang <congei42@163.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, horms@kernel.org,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
pabeni@redhat.com, louis.peens@corigine.com,
hui.zhou@corigine.com, oss-drivers@corigine.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] nfp: flower: fix use-after-free in neighbour update work
Date: Wed, 28 Oct 2026 10:20:04 +0000 [thread overview]
Message-ID: <179318280406.630848.412198034968801807.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261024044903.1130380-1-congei42@163.com>
Hello:
This patch was applied to netdev/net.git (main)
by Dave Miller <davem@davem-thinkpadp1gen8.ibmlond.csb>:
On Sat, 24 Oct 2026 12:49:03 +0800 you wrote:
> The netevent notifier handles neighbour updates and redirects by
> queuing nfp_tun_neigh_update() on system_highpri_wq. Each work item
> holds a reference to the neighbour, but only stores a pointer to the
> flower app.
>
> During device removal, nfp_tunnel_config_stop() unregisters the
> notifier. This waits for notifier callbacks to return, but does not
> wait for the work they queued. The teardown then frees app->priv and
> app without waiting for these work items. Flushing cmsg_work in
> nfp_flower_clean() does not cover the neighbour update work.
>
> [...]
Here is the summary with links:
- [net] nfp: flower: fix use-after-free in neighbour update work
https://git.kernel.org/netdev/net/c/083aaafd453c
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-10-28 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-24 4:49 [PATCH net] nfp: flower: fix use-after-free in neighbour update work Sicong Huang
2026-10-24 4:55 ` netdev-bot+sinfo
2026-10-27 12:38 ` Daniel Machon
2026-10-28 10: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=179318280406.630848.412198034968801807.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=congei42@163.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=hui.zhou@corigine.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.peens@corigine.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--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