From: Jakub Kicinski <kuba@kernel.org>
To: Li Chen <me@linux.beauty>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"Pasha Tatashin" <pasha.tatashin@soleen.com>,
"Mike Rapoport" <rppt@kernel.org>,
"Pratyush Yadav" <pratyush@kernel.org>,
"Eric Dumazet" <edumazet@google.com>,
"Neal Cardwell" <ncardwell@google.com>,
"Kuniyuki Iwashima" <kuniyu@google.com>,
"David S. Miller" <davem@davemloft.net>,
"David Ahern" <dsahern@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Borislav Petkov" <bp@alien8.de>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Pawan Gupta" <pawan.kumar.gupta@linux.intel.com>,
"Petr Mladek" <pmladek@suse.com>,
"Feng Tang" <feng.tang@linux.alibaba.com>,
"Kees Cook" <kees@kernel.org>,
"Li RongQing" <lirongqing@baidu.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Askar Safin" <safinaskar@gmail.com>,
"Frank van der Linden" <fvdl@google.com>,
"linux-doc" <linux-doc@vger.kernel.org>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
"netdev" <netdev@vger.kernel.org>
Subject: Re: [PATCH v1 3/3] liveupdate: suppress TCP RST during post-kexec restore window
Date: Mon, 2 Feb 2026 16:53:20 -0800 [thread overview]
Message-ID: <20260202165320.7ddb25f8@kernel.org> (raw)
In-Reply-To: <19c16df6e07.5d6555571430461.7492468111934043630@linux.beauty>
On Sun, 01 Feb 2026 09:44:27 +0800 Li Chen wrote:
> > On Fri, 30 Jan 2026 22:51:19 +0800 Li Chen wrote:
> > > During a kexec-based live update, userspace may restore established TCP
> > > connections after the new kernel has booted (e.g. via CRIU). Any packet
> > > arriving for a not-yet-restored socket will hit the no-socket path and
> > > trigger a TCP RST, causing the peer to immediately drop the connection.
> >
> > Can you not add a filter to simply drop those packets until workload is
> > running again? It'd actually be less racy than this hac^w patch ...
> >
>
> Thanks for the suggestion.
>
> When you say "add a filter", do you mean installing a temporary drop rule
> (nftables/iptables/tc) in the network domain which does not get rebooted by
> kexec (e.g. LB/ToR/host firewall), so packets never reach the new kernel
> until the workload is restored and ready?
>
> If you meant a filter inside the kexec'ed kernel, I'm worried it won't cover
> the critical window: kexec resets the ruleset, so we'd have to install the
> drop rule extremely early (initramfs) before any packets hit the no-socket
> path, which still seems inherently racy.
I'm not sure what your flow is exactly, but I assume you drive
the workload restore from user space already?
next prev parent reply other threads:[~2026-02-03 0:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 14:51 [PATCH v1 0/3] liveupdate: suppress TCP RST during post-kexec restore window Li Chen
2026-01-30 14:51 ` [PATCH v1 1/3] liveupdate: track " Li Chen
2026-01-30 14:51 ` [PATCH v1 2/3] liveupdate: bound and control " Li Chen
2026-01-30 14:51 ` [PATCH v1 3/3] liveupdate: suppress TCP RST during " Li Chen
2026-01-31 1:05 ` Jakub Kicinski
2026-02-01 1:44 ` Li Chen
2026-02-03 0:53 ` Jakub Kicinski [this message]
2026-02-03 3:15 ` Li Chen
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=20260202165320.7ddb25f8@kernel.org \
--to=kuba@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=feng.tang@linux.alibaba.com \
--cc=fvdl@google.com \
--cc=horms@kernel.org \
--cc=kees@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=me@linux.beauty \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pasha.tatashin@soleen.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pmladek@suse.com \
--cc=pratyush@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=safinaskar@gmail.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 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.