Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Chengfeng Ye" <nicoyip.dev@gmail.com>
Cc: "Christian Borntraeger" <borntraeger@linux.ibm.com>,
	linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org,
	"Heiko Carstens" <hca@linux.ibm.com>,
	"Vasily Gorbik" <gor@linux.ibm.com>,
	"Alexander Gordeev" <agordeev@linux.ibm.com>
Subject: Re: [PATCH net] net/smc: Serialize link activation with teardown
Date: Sun, 27 Sep 2026 07:57:47 +0000	[thread overview]
Message-ID: <20260927075748.5C52E1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260927074547.3694742-1-nicoyip.dev@gmail.com>

> smc_llc_link_active() marks a link active before scheduling its testlink
> work. The first-link confirmation paths call it without llc_conf_mutex,
> allowing link-down processing to clear the link between these operations:
> 
>   Connection setup                    Link-down worker
>   smc_llc_link_active()
>     link->state = SMC_LNK_ACTIVE
>                                       smcr_link_clear()
>                                         link->clearing = 1
>                                         smc_llc_link_clear()
>                                           cancel_delayed_work_sync()
>     schedule_delayed_work()
> 
> The connection reference keeps the link alive during activation, but the
> newly queued work outlives that reference. Later cleanup skips clearing
> [ ... ]
> without changing the handshake sequence or error handling.
> 
> Fixes: 877ae5be421d ("net/smc: periodic testlink support")
> 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/20260927074547.3694742-1-nicoyip.dev@gmail.com?part=1


  reply	other threads:[~2026-09-27  7:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27  7:45 [PATCH net] net/smc: Serialize link activation with teardown Chengfeng Ye
2026-09-27  7:57 ` sashiko-bot [this message]
2026-10-01  0: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=20260927075748.5C52E1F000FF@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