Netdev List
 help / color / mirror / Atom feed
From: Ayush Sawal <ayush.sawal@chelsio.com>
To: Sang-Hoon Choi <csh0052@gmail.com>
Cc: netdev@vger.kernel.org, Changyul Lee <lcy8047@gmail.com>
Subject: Re: [PATCH net] cxgb4/ch_ktls: disable softirqs around tid_list erases
Date: Thu, 1 Oct 2026 18:17:52 +0530	[thread overview]
Message-ID: <03db0cd6-6a39-4cb0-a8f5-cb0d1e2b7663@chelsio.com> (raw)
In-Reply-To: <179070264839.12871.11715792321728503844.idr-bug-51@gmail.com>


On 29-09-2026 23:07, Sang-Hoon Choi wrote:
> chcr_ktls_cpl_act_open_rpl() inserts into tid_list from the receive path
> using xa_insert_bh().  The array is shared by the adapter's connections
> and initialized with XA_FLAGS_LOCK_BH.  However, chcr_ktls_dev_del() and
> the chcr_ktls_dev_add() error path use xa_erase(), which takes the XArray
> lock without disabling softirqs.
>
> When cleanup runs with softirqs enabled, a receive softirq for another
> connection on the same CPU can interrupt the erase and spin on the lock
> held by the interrupted task.  Use xa_erase_bh() at both sites to match
> the insertion path.
>
> Fixes: 65e302a9bd57 ("cxgb4/ch_ktls: Clear resources when pf4 device is removed")
> Reported-by: Changyul Lee <lcy8047@gmail.com>
> Assisted-by: LLM
> Signed-off-by: Sang-Hoon Choi <csh0052@gmail.com>
> ---
> Compile-tested with x86_64 allmodconfig and W=1.
> I have not tested this on Chelsio hardware.
>
>   drivers/net/ethernet/chelsio/inline_crypto/ch_ktls/chcr_ktls.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/chelsio/inline_crypto/ch_ktls/chcr_ktls.c b/drivers/net/ethernet/chelsio/inline_crypto/ch_ktls/chcr_ktls.c
> index f5acd4be1e69dcb551758dd27808a1b1eec374bd..dbec95b4977736b9b2fefdf5648a7eaca16429cb 100644
> --- a/drivers/net/ethernet/chelsio/inline_crypto/ch_ktls/chcr_ktls.c
> +++ b/drivers/net/ethernet/chelsio/inline_crypto/ch_ktls/chcr_ktls.c
> @@ -389,7 +389,7 @@ static void chcr_ktls_dev_del(struct net_device *netdev,
>   		cxgb4_remove_tid(&tx_info->adap->tids, tx_info->tx_chan,
>   				 tx_info->tid, tx_info->ip_family);
>   
> -		xa_erase(&u_ctx->tid_list, tx_info->tid);
> +		xa_erase_bh(&u_ctx->tid_list, tx_info->tid);
>   	}
>   
>   	port_stats = &tx_info->adap->ch_ktls_stats.ktls_port[tx_info->port_id];
> @@ -577,7 +577,7 @@ static int chcr_ktls_dev_add(struct net_device *netdev, struct sock *sk,
>   	cxgb4_remove_tid(&tx_info->adap->tids, tx_info->tx_chan,
>   			 tx_info->tid, tx_info->ip_family);
>   
> -	xa_erase(&u_ctx->tid_list, tx_info->tid);
> +	xa_erase_bh(&u_ctx->tid_list, tx_info->tid);
>   
>   put_module:
>   	/* release module refcount */
Thanks for the patch. Because of the uld_mutex taken in
cxgb4_ktls_dev_add/del, this issue was not coming, but the
change is correct and keeps the locking consistent with
XA_FLAGS_LOCK_BH.

Reviewed-by: Ayush Sawal <ayush.sawal@chelsio.com>

  reply	other threads:[~2026-10-01 12:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 17:37 [PATCH net] cxgb4/ch_ktls: disable softirqs around tid_list erases Sang-Hoon Choi
2026-10-01 12:47 ` Ayush Sawal [this message]
2026-10-02  9: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=03db0cd6-6a39-4cb0-a8f5-cb0d1e2b7663@chelsio.com \
    --to=ayush.sawal@chelsio.com \
    --cc=csh0052@gmail.com \
    --cc=lcy8047@gmail.com \
    --cc=netdev@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox