From: Jakub Kicinski <kuba@kernel.org>
To: Roshan Kumar <roshaen09@gmail.com>
Cc: netdev@vger.kernel.org, steffen.klassert@secunet.com,
herbert@gondor.apana.org.au, davem@davemloft.net,
edumazet@kernel.org, pabeni@redhat.com, horms@kernel.org,
chopps@labn.net, linux-kernel@vger.kernel.org,
lilly@aronleigh.au, shubham@octane.security, gio@octane.security,
robert@octane.security, paolo@octane.security
Subject: Re: [PATCH net v3 0/2] xfrm: iptfs: fix queued receive state lifetime
Date: Mon, 5 Oct 2026 18:31:41 -0700 [thread overview]
Message-ID: <20261005183141.5e246d3e@kernel.org> (raw)
In-Reply-To: <20260930050307.1978654-1-roshaen09@gmail.com>
On Wed, 30 Sep 2026 10:33:05 +0530 Roshan Kumar wrote:
> IP-TFS can retain received skbs in its reorder window and reassembly state.
> Two lifetime problems interact in these paths: the shared drop timer
> does not track the two states independently, and retained skbs do not
> keep their input net_device alive.
net/xfrm/xfrm_iptfs.c:1346:2-12: WARNING: NULL check before
(net)dev_{put,hold} functions is not needed.
prev parent reply other threads:[~2026-10-06 1:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 5:03 Roshan Kumar
2026-09-30 5:03 ` [PATCH net v3 1/2] xfrm: iptfs: track independent drop deadlines Roshan Kumar
2026-10-04 5:22 ` netdev-bot+sashiko
2026-09-30 5:03 ` [PATCH net v3 2/2] xfrm: iptfs: hold a device reference while packets are queued Roshan Kumar
2026-10-04 5:22 ` netdev-bot+sashiko
2026-09-30 5:09 ` [PATCH net v3 0/2] xfrm: iptfs: fix queued receive state lifetime netdev-bot+sinfo
2026-10-06 1:31 ` Jakub Kicinski [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=20261005183141.5e246d3e@kernel.org \
--to=kuba@kernel.org \
--cc=chopps@labn.net \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=gio@octane.security \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=lilly@aronleigh.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paolo@octane.security \
--cc=robert@octane.security \
--cc=roshaen09@gmail.com \
--cc=shubham@octane.security \
--cc=steffen.klassert@secunet.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
all inboxes | Powered by JetHome®