From: sashiko-bot@kernel.org
To: "Mahanta Jambigi" <mjambigi@linux.ibm.com>
Cc: "Christian Borntraeger" <borntraeger@linux.ibm.com>,
linux-s390@vger.kernel.org,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>
Subject: Re: [PATCH net] net/smc: serialize clcsock teardown in smc_accept_dequeue
Date: Mon, 24 Aug 2026 07:08:55 +0000 [thread overview]
Message-ID: <20260824070855.D93241F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260824065851.1070988-1-mjambigi@linux.ibm.com>
> smc_accept_dequeue() open-codes clcsock teardown for SMC_CLOSED child sockets
> without taking clcsock_release_lock:
>
> new_sk->sk_prot->unhash(new_sk);
> if (isk->clcsock) {
> sock_release(isk->clcsock);
> isk->clcsock = NULL;
> }
>
> This bypasses the clcsock_release_lock discipline used elsewhere in SMC clcsock
> lifetime handling. In particular, other paths serialize clcsock access and
> updates with clcsock_release_lock, but this local teardown path does not.
>
> Fix it by taking clcsock_release_lock around the local teardown and by storing
> NULL before sock_release(), matching the established ordering used by other
> clcsock teardown paths.
>
> Fixes: 127f49705823 ("net/smc: release clcsock from tcp_listen_worker")
> Reviewed-by: Hidayath Khan <hidayath@linux.ibm.com>
> Signed-off-by: Mahanta Jambigi <mjambigi@linux.ibm.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260824065851.1070988-1-mjambigi@linux.ibm.com?part=1
next prev parent reply other threads:[~2026-08-24 7:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 6:58 [PATCH net] net/smc: serialize clcsock teardown in smc_accept_dequeue Mahanta Jambigi
2026-08-24 7:08 ` sashiko-bot [this message]
2026-08-26 3:18 ` Dust Li
2026-08-26 9:12 ` Mahanta Jambigi
2026-08-27 14:07 ` Dust Li
2026-08-28 11:18 ` Mahanta Jambigi
2026-08-31 12:43 ` Dust Li
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=20260824070855.D93241F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=mjambigi@linux.ibm.com \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.