From: Simon Horman <horms@kernel.org>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: Wentao Liang <vulab@iscas.ac.cn>,
andrew+netdev@lunn.ch, ayush.sawal@chelsio.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, rohitm@chelsio.com, stable@vger.kernel.org
Subject: Re: [PATCH] chtls: Fix skb reference leak in chtls_send_reset()
Date: Mon, 21 Sep 2026 13:13:42 +0100 [thread overview]
Message-ID: <20260921121342.GL13925@horms.kernel.org> (raw)
In-Reply-To: <arAJCMpzSVKDiLqe@krikkit>
On Sun, Sep 20, 2026 at 06:25:44PM +0200, Sabrina Dubroca wrote:
> 2026-09-19, 09:04:28 +0100, Simon Horman wrote:
> > > diff --git a/drivers/net/ethernet/chelsio/inline_crypto/chtls/chtls_cm.c b/drivers/net/ethernet/chelsio/inline_crypto/chtls/chtls_cm.c
> > > index 0e3e5cf52c2c..a363f20452fa 100644
> > > --- a/drivers/net/ethernet/chelsio/inline_crypto/chtls/chtls_cm.c
> > > +++ b/drivers/net/ethernet/chelsio/inline_crypto/chtls/chtls_cm.c
> > > @@ -265,12 +265,14 @@ static void chtls_send_reset(struct sock *sk, int mode, struct sk_buff *skb)
> > > chtls_purge_write_queue(sk);
> > >
> > > csk_set_flag(csk, CSK_ABORT_SHUTDOWN);
> > > - if (sk->sk_state != TCP_SYN_RECV)
> > > + if (sk->sk_state != TCP_SYN_RECV) {
> > > chtls_send_abort(sk, mode, skb);
> > > - else
> > > + } else {
> > > chtls_set_tcb_field_rpl_skb(sk, TCB_T_FLAGS_W,
> > > TCB_T_FLAGS_V(TCB_T_FLAGS_M), 0,
> > > TCB_FIELD_COOKIE_TFLAG, 1);
> > > + kfree_skb(skb);
> > > + }
> > >
> > > return;
> > > out:
> >
> > This code change looks reasonable to me.
> > But the driver was removed in v7.2 by
> > cdae65fc43f2 ("tls: remove tls_toe and the related driver")
> > And, as a result it didn't run through our CI.
> >
> > So while I think it could go to stable
> > It probably needs more eyes on it.
>
> But there isn't anyone around that has even a remote understanding of
> what this driver does... Since stable@ seems willing to take patches
> that remove broken features [1], maybe we should just do that?
Sure, that would address my concern regarding how to handle this quite nicely.
>
> [1] https://lore.kernel.org/netdev/apbqjuv6l20bTjQI@laps/
>
> --
> Sabrina
prev parent reply other threads:[~2026-09-21 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 10:58 Wentao Liang
2026-09-19 8:04 ` Simon Horman
2026-09-20 16:25 ` Sabrina Dubroca
2026-09-21 12:13 ` Simon Horman [this message]
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=20260921121342.GL13925@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ayush.sawal@chelsio.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rohitm@chelsio.com \
--cc=sd@queasysnail.net \
--cc=stable@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/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
all inboxes | Powered by JetHome®