From: Dust Li <dust.li@linux.alibaba.com>
To: tikipiya0531 <tikipiya0531@proton.me>,
"alibuda@linux.alibaba.com" <alibuda@linux.alibaba.com>,
"sidraya@linux.ibm.com" <sidraya@linux.ibm.com>,
"mjambigi@linux.ibm.com" <mjambigi@linux.ibm.com>
Cc: "linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [net/smc] clcsock_release_lock not held on fallback poll/sendmsg/... (follow-up to 64a6b36b)
Date: Mon, 19 Oct 2026 15:56:08 +0800 [thread overview]
Message-ID: <atXNGOXEMZLlaRFH@linux.alibaba.com> (raw)
In-Reply-To: <Raqdw_agFcPtAnTmvvz2owgVpblVtRzIrVJdEpHDL4PYX7qC9ULPfcFRyimT6NUQmTf9f17Gp_nawYoiqOwPUM45xtk8G9OK_LjiTgZxG7s=@proton.me>
On 2026-10-18 14:47:41, tikipiya0531 wrote:
>Hello,
>
>Please find the full write-up attached as report-en.md (same content
>summarized below for quick triage).
>
>Summary
>-------
>Commit 64a6b36b0e18 ("net/smc: protect clcsock lifetime in smc_getname")
>added clcsock_release_lock around smc_getname() because link-group teardown
>can call smc_clcsock_release() while the SMC socket is still open. The same
>unlocked smc->clcsock access pattern still exists on several other paths that
>touch the CLC socket in fallback mode (and in SOCK_DIAG fill), without holding
>clcsock_release_lock.
>
>I am not claiming a reliable exploit on current mainline; I am asking for a
>small hardening sweep similar to 64a6b36b and c0bf3d8a943b.
Hi tikipiya0531,
If you are asking for a patch, please send a patch with real bug evidence
in the commit message.
The report you sent looks like a mess of AI-generated things without your
understanding.
Best regards,
Dust
prev parent reply other threads:[~2026-10-19 7:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 14:47 [net/smc] clcsock_release_lock not held on fallback poll/sendmsg/... (follow-up to 64a6b36b) tikipiya0531
2026-10-19 7:56 ` Dust Li [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=atXNGOXEMZLlaRFH@linux.alibaba.com \
--to=dust.li@linux.alibaba.com \
--cc=alibuda@linux.alibaba.com \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjambigi@linux.ibm.com \
--cc=sidraya@linux.ibm.com \
--cc=tikipiya0531@proton.me \
/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.