From: Roshan Kumar <roshaen09@gmail.com>
To: steffen.klassert@secunet.com
Cc: lilly@aronleigh.au, herbert@gondor.apana.org.au,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, chopps@labn.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3] xfrm: iptfs: avoid canceling reorder window drop timer
Date: Tue, 29 Sep 2026 04:03:28 +0000 [thread overview]
Message-ID: <179065460863.1915782.14730367973310266066@gmail.com> (raw)
In-Reply-To: <apaRiWQn54Pr9hpm@secunet.com>
Lilly, thanks for working on this. I need the same timer correction as a
prerequisite for the queued skb device lifetime fix.
While testing the interaction reported by Steffen/Sashiko, I reproduced a
second problem with only skipping the cancellation: a timer armed for a
completed reassembly can retain its old deadline and expire a subsequent
reassembly too early. The runt created reassembly path also needs to arm the
timer.
I have a version which records separate absolute deadlines for reassembly and
the reorder window, arms their shared hrtimer for the earlier deadline, and
expires only state whose own deadline has passed. A regression starts one
reassembly, queues a later reorder entry near its deadline, completes the
first reassembly, and verifies that the reorder entry remains until its own
deadline.
That regression now passes on both the regular KASAN and reference tracker
kernel and an enhanced lockdep and RCU debug kernel, with the queued entry
retained for its full five second interval. The runt created reassembly
regression passes as well.
I am preparing that as patch 1 of a two patch net series, retaining your
reporting credit and links to this patch and the review. If you would prefer to
post the corrected timer patch as v4 yourself, please say so and I will base
the device lifetime patch on it instead.
prev parent reply other threads:[~2026-09-29 4:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 7:28 [PATCH net v3] xfrm: iptfs: avoid canceling reorder-window " Lilly Aronleigh
2026-09-01 8:49 ` Steffen Klassert
2026-09-29 4:03 ` Roshan Kumar [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=179065460863.1915782.14730367973310266066@gmail.com \
--to=roshaen09@gmail.com \
--cc=chopps@labn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=lilly@aronleigh.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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®