Linux s390 Architecture development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Sabrina Dubroca" <sd@queasysnail.net>
Cc: "Alexander Gordeev" <agordeev@linux.ibm.com>,
	"Heiko Carstens" <hca@linux.ibm.com>,
	linux-s390@vger.kernel.org, "Vasily Gorbik" <gor@linux.ibm.com>
Subject: Re: [PATCH net-next 1/2] tls: remove tls_toe and the related driver
Date: Wed, 10 Jun 2026 14:21:46 +0000	[thread overview]
Message-ID: <20260610142147.5352C1F00898@smtp.kernel.org> (raw)
In-Reply-To: <c3c9ae09580a5c1d36b32b5ab3a5db398feddfe3.1781013810.git.sd@queasysnail.net>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Incomplete removal of the `tls_toe` feature leaves behind dangling feature flags (`NETIF_F_HW_TLS_RECORD`) and upper layer driver references (`CXGB4_ULD_TLS`), leading to dead code and false feature advertisement to userspace.
--

commit 9a055c5cc4ab72cb186cfa373957ed0d0080f2d2
Author: Sabrina Dubroca <sd@queasysnail.net>

tls: remove tls_toe and the related driver

This patch removes the unmaintained tls_toe feature and its single user,
the chelsio chtls driver. It removes the related documentation, Kconfig
options, and source files.

> diff --git a/net/tls/Kconfig b/net/tls/Kconfig
> index a25bf57f26738..4f4d5973a28f4 100644
> --- a/net/tls/Kconfig
> +++ b/net/tls/Kconfig
> @@ -27,13 +27,3 @@ config TLS_DEVICE
>  	Enable kernel support for HW offload of the TLS protocol.
>  
>  	If unsure, say N.
> -
> -config TLS_TOE
> -	bool "Transport Layer Security TCP stack bypass"
> -	depends on TLS
> -	default n
> -	help
> -	Enable kernel support for legacy HW offload of the TLS protocol,
> -	which is incompatible with the Linux networking stack semantics.
> -
> -	If unsure, say N.

[Severity: Low]
Since this removes the tls_toe feature and the chtls driver, should we also
clean up the remaining references to the hardware TLS record offload?

For example, the feature bit NETIF_F_HW_TLS_RECORD_BIT is still present in
include/linux/netdev_features.h, and its corresponding ethtool string 
"tls-hw-record" remains in net/ethtool/common.c.

Also, the cxgb4 driver still unconditionally adds NETIF_F_HW_TLS_RECORD to
netdev->hw_features in cxgb4_main.c:init_one(), which could lead to devices
falsely advertising this removed capability to userspace.

Additionally, CXGB4_ULD_TLS is left behind in enum cxgb4_uld
(drivers/net/ethernet/chelsio/cxgb4/cxgb4_uld.h), and there is dead code
processing it in drivers/net/ethernet/chelsio/cxgb4/cxgb4_debugfs.c
inside sge_qinfo_show() and in drivers/net/ethernet/chelsio/cxgb4/cudbg_lib.h
inside cudbg_uld_rxq_to_qtype().

Could these leftovers be removed as well to complete the cleanup?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1781013810.git.sd@queasysnail.net?part=1

      parent reply	other threads:[~2026-06-10 14:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1781013810.git.sd@queasysnail.net>
2026-06-09 14:21 ` [PATCH net-next 1/2] tls: remove tls_toe and the related driver Sabrina Dubroca
2026-06-10  4:04   ` Eric Dumazet
2026-06-10 14:21   ` sashiko-bot [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=20260610142147.5352C1F00898@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=sd@queasysnail.net \
    /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