Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hyunwoo Kim <imv4bel@gmail.com>
Cc: dsahern@kernel.org, idosch@nvidia.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, stable@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net v2] inet: frags: fix use-after-free caused by the fqdir_pre_exit() flush
Date: Fri, 05 Jun 2026 01:10:07 +0000	[thread overview]
Message-ID: <178062180740.3088134.15315966161183753620.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ah6ukYq5G98LshdA@v4bel>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 2 Jun 2026 19:21:05 +0900 you wrote:
> On netns teardown, fqdir_pre_exit() walks the fqdir rhashtable and
> flushes every fragment queue that is not yet complete using
> inet_frag_queue_flush(). That helper frees all the skbs queued on the
> fragment queue but does not set INET_FRAG_COMPLETE, and leaves
> q->fragments_tail and q->last_run_head pointing at the freed skbs.
> The queue itself stays in the rhashtable.
> 
> [...]

Here is the summary with links:
  - [net,v2] inet: frags: fix use-after-free caused by the fqdir_pre_exit() flush
    https://git.kernel.org/netdev/net/c/32594b098549

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-06-05  1:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02 10:21 [PATCH net v2] inet: frags: fix use-after-free caused by the fqdir_pre_exit() flush Hyunwoo Kim
2026-06-05  1: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=178062180740.3088134.15315966161183753620.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=imv4bel@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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