From: Jakub Kicinski <kuba@kernel.org>
To: Xin Long <lucien.xin@gmail.com>
Cc: luoqing <l1138897701@163.com>,
davem@davemloft.net, edumazet@google.com, horms@kernel.org,
linux-kernel@vger.kernel.org, linux-sctp@vger.kernel.org,
marcelo.leitner@gmail.com, netdev@vger.kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH net-next v5] sctp: auth: discard auth_chunk when skb_clone fails
Date: Wed, 29 Jul 2026 16:35:42 -0700 [thread overview]
Message-ID: <20260729163542.4d3bea9a@kernel.org> (raw)
In-Reply-To: <CADvbK_cAR8qZwA1pAN1Kov+v-Whg_P19VK-Fzpztxc5fiwA+Pg@mail.gmail.com>
On Wed, 29 Jul 2026 10:43:26 -0400 Xin Long wrote:
> > > When processing AUTH + COOKIE-ECHO packets, if skb_clone() fails
> > > due to memory pressure, chunk->auth_chunk is NULL. The original
> > > code still sets chunk->auth = 1 and continues, leaving the
> > > COOKIE-ECHO to be processed without a valid auth_chunk for
> > > deferred verification.
> > >
> > > Discard the AUTH chunk early via pdiscard when skb_clone() fails,
> > > so that the receive loop can continue processing remaining chunks
> > > in the inqueue instead of stalling the entire packet.
> >
> > Hi Xin Long, should we apply this or it's no longer worth it after
> > 8e04823c120b ?
> >
> Apply it to net-next.git.
>
> Acked-by: Xin Long <lucien.xin@gmail.com>
Thanks!
> So sending patches with wrong in-reply-to doesn't require repost?
If patchwork ingests the series correctly (which is usually does
for single patch postings) there's no need to resend. It's mostly
a convenience thing for maintainers since we try to process patches
from oldest and the threading makes the sort harder.
next prev parent reply other threads:[~2026-07-29 23:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 1:55 [PATCH v4 net-next] sctp: auth: break when skb_clone fails for auth_chunk luoqing
2026-07-21 1:55 ` [PATCH v4 net] sctp: auth: verify auth requirement when auth_chunk is NULL luoqing
2026-07-22 17:37 ` Xin Long
2026-07-22 21:00 ` patchwork-bot+netdevbpf
2026-07-22 18:31 ` [PATCH v4 net-next] sctp: auth: break when skb_clone fails for auth_chunk Xin Long
2026-07-23 6:11 ` [PATCH net-next v5] sctp: auth: discard auth_chunk when skb_clone fails luoqing
2026-07-23 17:16 ` Jakub Kicinski
2026-07-29 1:23 ` Jakub Kicinski
2026-07-29 14:43 ` Xin Long
2026-07-29 23:35 ` Jakub Kicinski [this message]
2026-07-30 0:00 ` 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=20260729163542.4d3bea9a@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=l1138897701@163.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 \
/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