From: sashiko-bot@kernel.org
To: "Chengfeng Ye" <nicoyip.dev@gmail.com>
Cc: "Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
linux-s390@vger.kernel.org,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH net] net/smc: Serialize CLC preparation with link teardown
Date: Sun, 27 Sep 2026 07:57:12 +0000 [thread overview]
Message-ID: <20260927075712.69DEC1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260927074600.3694802-1-nicoyip.dev@gmail.com>
> smcr_clc_prep_confirm_accept() reads the RMB memory region and scatterlist
> without holding llc_conf_mutex. The connection's link reference keeps the
> link object alive, but does not prevent smcr_link_clear() from unmapping
> its buffers and destroying its RDMA resources.
>
> The CLC handshake can load the scatterlist pointer, then an LLC delete-link
> worker can acquire llc_conf_mutex for writing and free the scatterlist in
> smcr_buf_unmap_link(). When the handshake resumes, sg_dma_address() reads
> freed memory. The memory-region rkey read has the same lifetime problem.
>
> KASAN reported:
>
> BUG: KASAN: slab-use-after-free in smc_clc_send_confirm_accept
> Read of size 8 at addr ffff88810efcdfd0 by task poc/94
> Call Trace:
> [ ... ]
> retain priority.
>
> Fixes: 541afa10c126 ("net/smc: add smcr_port_err() and smcr_link_down() processing")
> 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/20260927074600.3694802-1-nicoyip.dev@gmail.com?part=1
next prev parent reply other threads:[~2026-09-27 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 7:46 [PATCH net] net/smc: Serialize CLC preparation with link teardown Chengfeng Ye
2026-09-27 7:57 ` sashiko-bot [this message]
2026-09-30 0:48 ` netdev-bot+sashiko
2026-10-03 19:49 ` 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=20260927075712.69DEC1F000FF@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 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.