From: sashiko-bot@kernel.org
To: "Chengfeng Ye" <nicoyip.dev@gmail.com>
Cc: "Vasily Gorbik" <gor@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>
Subject: Re: [PATCH net] net/smc: Serialize early link group cleanup with termination
Date: Sun, 27 Sep 2026 06:52:03 +0000 [thread overview]
Message-ID: <20260927065204.54AA51F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260927063607.3691520-1-nicoyip.dev@gmail.com>
> smc_lgr_cleanup_early() calls __smc_lgr_terminate() without checking or
> setting lgr->freeing. A concurrent smc_lgr_terminate_sched() can claim
> freeing and queue terminate_work before early cleanup takes lgr_lock.
> Early cleanup still enters __smc_lgr_terminate(), where both callers can
> observe lgr->terminating clear before either sets it. Both then tear down
> the same link group, causing use-after-free and duplicate resource release.
>
> KASAN reported:
>
> BUG: KASAN: use-after-free in __smc_lgr_terminate+0x393/0x3a0
> Write of size 1 at addr ffff8880bf2c0300 by task poc/106
> Call Trace:
> __smc_lgr_terminate+0x393/0x3a0
> __smc_connect+0x2e3d/0x4930
> smc_connect+0x42c/0x580
> [ ... ]
> group alive until early cleanup has checked teardown ownership.
>
> Fixes: f9aab6f2ce57 ("net/smc: immediate freeing in smc_lgr_cleanup_early()")
> Cc: stable@vger.kernel.org
> Signed-off-by: Chengfeng Ye <nicoyip.dev@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260927063607.3691520-1-nicoyip.dev@gmail.com?part=1
next prev parent reply other threads:[~2026-09-27 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 6:36 [PATCH net] net/smc: Serialize early link group cleanup with termination Chengfeng Ye
2026-09-27 6:52 ` sashiko-bot [this message]
2026-09-30 0:38 ` netdev-bot+sashiko
2026-10-03 19:37 ` Chengfeng Ye
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=20260927065204.54AA51F000FF@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-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nicoyip.dev@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox