From: Jakub Kicinski <kuba@kernel.org>
To: Xin Long <lucien.xin@gmail.com>
Cc: Jun Yang <1753810072@qq.com>,
netdev@vger.kernel.org,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
linux-sctp@vger.kernel.org, linux-kernel@vger.kernel.org,
Jun Yang <junvyyang@tencent.com>,
stable@kernel.org
Subject: Re: [PATCH net v3] sctp: don't free the ASCONF's own transport in DEL-IP processing
Date: Thu, 23 Jul 2026 10:35:15 -0700 [thread overview]
Message-ID: <20260723103515.0059802b@kernel.org> (raw)
In-Reply-To: <CADvbK_fjH_XGMVjZGXAk_Zj6_GOHu3u2bj9wOSMRymwNMK-k5g@mail.gmail.com>
On Thu, 23 Jul 2026 11:33:27 -0400 Xin Long wrote:
> On Thu, Jul 23, 2026 at 10:29 AM Jakub Kicinski <kuba@kernel.org> wrote:
> >
> > On Tue, 21 Jul 2026 21:14:05 +0800 Jun Yang wrote:
> > > Acked-by: Xin Long <lucien.xin@gmail.com>
> >
> > Could you point me to where Xin Long acked this?
> > I don't see the ack in replies to v1 or v2.
>
> He initially sent the patch to security@kernel.org, and I asked him to
> submit it to netdev with my Ack.
Got it, thanks!
> By the way, there's a question about whether patches for security fixes
> should include the PoC in the patch/cover-letter when they're posted to
> the netdev ML?
Not sure if there's an official policy on this but IMHO they should be
easily accessible to reviewers / maintainers. If a frontier LLM can
generate an exploit for the problem based on the patch, hiding the
repro buys us nothing. And often the repro is useful during review.
For me an ideal submission would contain just a description of how the
bug was triggered in testing in the commit message, and a link to the
repro / PoC under the --- marker.
next prev parent reply other threads:[~2026-07-23 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 13:14 [PATCH net v3] sctp: don't free the ASCONF's own transport in DEL-IP processing Jun Yang
2026-07-23 14:29 ` Jakub Kicinski
2026-07-23 15:33 ` Xin Long
2026-07-23 17:35 ` Jakub Kicinski [this message]
2026-07-23 17:40 ` patchwork-bot+netdevbpf
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=20260723103515.0059802b@kernel.org \
--to=kuba@kernel.org \
--cc=1753810072@qq.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=junvyyang@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@kernel.org \
/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.