Re: [PATCH net v3] sctp: don't free the ASCONF's own transport in DEL-IP processing

Jakub Kicinski <[email protected]> Thu, 23 Jul 2026 10:35:15 -0700
Newsgroups org.kernel.vger.linux-sctp,org.kernel.vger.linux-kernel,org.kernel.vger.netdev
Message-ID <[email protected]>
On Thu, 23 Jul 2026 11:33:27 -0400 Xin Long wrote:
> On Thu, Jul 23, 2026 at 10:29=E2=80=AFAM Jakub Kicinski <[email protected]>=
 wrote:
> >
> > On Tue, 21 Jul 2026 21:14:05 +0800 Jun Yang wrote: =20
> > > Acked-by: Xin Long <[email protected]> =20
> >
> > Could you point me to where Xin Long acked this?
> > I don't see the ack in replies to v1 or v2. =20
>=20
> He initially sent the patch to [email protected], 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.