From: sashiko-bot@kernel.org
To: "Chengfeng Ye" <nicoyip.dev@gmail.com>
Cc: linux-rdma@vger.kernel.org, "Vasily Gorbik" <gor@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
linux-s390@vger.kernel.org, "Heiko Carstens" <hca@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>
Subject: Re: [PATCH net] net/smc: serialize link group free work scheduling
Date: Sun, 27 Sep 2026 07:57:06 +0000 [thread overview]
Message-ID: <20260927075706.8314A1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260927074520.3694663-1-nicoyip.dev@gmail.com>
> smc_lgr_schedule_free_work() checks lgr->freeing without the link group
> list lock held by the teardown paths. A concurrent smc_lgr_free_work()
> can set freeing and cancel the delayed work between that check and
> mod_delayed_work(), leaving a timer pending on a freed link group:
>
> CPU 0 (smc_conn_free) CPU 1 (smc_lgr_free_work)
> observe lgr->freeing == 0
> set lgr->freeing under lgr_lock
> cancel_delayed_work()
> smc_lgr_free(): drop lgr reference
> mod_delayed_work()
> smc_lgr_put(): drop last reference and free lgr
>
> When the timer expires, the timer core accesses the freed memory.
> KASAN reported:
> [ ... ]
> scheduling, keeping the group alive while acquiring the lock.
>
> Fixes: 8e316b9e7260 ("net/smc: improve link group freeing")
> 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/20260927074520.3694663-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:45 [PATCH net] net/smc: serialize link group free work scheduling Chengfeng Ye
2026-09-27 7:57 ` sashiko-bot [this message]
2026-09-30 0:45 ` netdev-bot+sashiko
2026-10-03 19:46 ` 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=20260927075706.8314A1F000FF@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.