From: patchwork-bot+netdevbpf@kernel.org
To: Yilin Zhang <yilinzhang@moonshot.ai>
Cc: edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, bug-report@moonshot.ai,
shiweiming@moonshot.ai
Subject: Re: [PATCH v2] inet: frags: invalidate queues before flushing them
Date: Thu, 10 Sep 2026 01:00:04 +0000 [thread overview]
Message-ID: <178900200463.1131357.2032127339947818719.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260904162800.1095662-1-yilinzhang@moonshot.ai>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 5 Sep 2026 00:28:00 +0800 you wrote:
> fqdir_pre_exit() flushes the skbs from incomplete queues without
> changing their completion state. A fragment which found a queue before
> high_thresh was cleared can then acquire the queue lock and reuse stale
> reassembly metadata. A queue concurrently killed after fqdir->dead is
> set can instead become INET_FRAG_COMPLETE|INET_FRAG_HASH_DEAD while
> still holding its old skbs; skipping it because it is complete leaves
> those references behind until asynchronous fqdir teardown.
>
> [...]
Here is the summary with links:
- [v2] inet: frags: invalidate queues before flushing them
https://git.kernel.org/netdev/net/c/b824476c56a1
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-09-10 1:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 16:28 [PATCH v2] inet: frags: invalidate queues before flushing them Yilin Zhang
2026-09-10 1: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=178900200463.1131357.2032127339947818719.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bug-report@moonshot.ai \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shiweiming@moonshot.ai \
--cc=stable@vger.kernel.org \
--cc=yilinzhang@moonshot.ai \
/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.