From: Artem Lytkin <iprintercanon@gmail.com>
To: Zixuan Chai <petalzu987@gmail.com>
Cc: Ido Schimmel <idosch@nvidia.com>,
David Ahern <dsahern@kernel.org>,
Kuniyuki Iwashima <kuniyu@google.com>,
Eric Dumazet <edumazet@google.com>, Ren Wei <weir@nebusec.ai>,
netdev@vger.kernel.org
Subject: Re: [PATCH net v2 1/1] ip6_tunnel: snapshot encap in xmit
Date: Tue, 25 Aug 2026 12:08:42 +0300 [thread overview]
Message-ID: <20260825090843.64570-1-iprintercanon@gmail.com> (raw)
In-Reply-To: <CADTzadL++bLiuYUrzDYmTbEf+bb=hkT-bxBQYCtxZscF5Z6oxA@mail.gmail.com>
On Tue, Aug 25, 2026 at 03:23:42PM +0800, Zixuan Chai wrote:
> 1. take this minimal fix through net for the crash, and do the RCU config
> conversion separately in net-next; or
> 2. follow your proposed approach and address this as part of the RCU
> config conversion.
1. The conversion is net-next only and can't be backported, and your
Fixes: points at a 2016 commit, so the crash needs its own fix in net
anyway. I'll rebase on v3 once it's in; that's a few lines in
ip6_tnl_xmit().
> Reported-by: Zixuan Chai <petalzu987@gmail.com>
> Reported-by: Vega <vega@nebusec.ai>
Sure, on the patch that handles the half-applied encap on a rejected
changelink, which v3 doesn't cover, with a Closes: to your report.
Artem
next prev parent reply other threads:[~2026-08-25 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 8:40 [PATCH net v2 0/1] ip6_tunnel: snapshot encap in xmit Ren Wei
2026-08-08 8:40 ` [PATCH net v2 1/1] " Ren Wei
2026-08-08 19:38 ` Kuniyuki Iwashima
2026-08-09 12:33 ` Ido Schimmel
2026-08-24 19:47 ` Artem Lytkin
2026-08-25 7:23 ` Zixuan Chai
2026-08-25 9:08 ` Artem Lytkin [this message]
2026-08-09 13:46 ` Ido Schimmel
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=20260825090843.64570-1-iprintercanon@gmail.com \
--to=iprintercanon@gmail.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=petalzu987@gmail.com \
--cc=weir@nebusec.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.