From: sashiko-bot@kernel.org
To: "Ankur Arora" <ankur.a.arora@oracle.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH v14 05/15] arm64: rqspinlock: Remove private copy of smp_cond_load_acquire_timewait()
Date: Tue, 14 Jul 2026 07:44:06 +0000 [thread overview]
Message-ID: <20260714074406.95EDF1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260714073041.40250-6-ankur.a.arora@oracle.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Removing the ARM64-specific `smp_cond_load_acquire_timewait()` fallback before replacing it with a working alternative breaks BPF `rqspinlock` timeout functionality, causing indefinite hangs on platforms without a timer event stream.
--
--- Patch [5]: [PATCH v14 05/15] arm64: rqspinlock: Remove private copy of smp_cond_load_acquire_timewait() ---
commit e150f6dc634a9b6af6666a67d9bc5ea262bedad7
Author: Ankur Arora <ankur.a.arora@oracle.com>
arm64: rqspinlock: Remove private copy of smp_cond_load_acquire_timewait()
This commit removes the private definition of smp_cond_load_acquire_timewait()
and its helper macros from arch/arm64/include/asm/rqspinlock.h. The commit
message notes this is in preparation for defining
smp_cond_load_acquire_timeout(), allowing rqspinlock to fall back to using
smp_cond_load_acquire() in the interim.
> diff --git a/arch/arm64/include/asm/rqspinlock.h b/arch/arm64/include/asm/rqspinlock.h
> index 9ea0a74e58927..a385603436e98 100644
> --- a/arch/arm64/include/asm/rqspinlock.h
> +++ b/arch/arm64/include/asm/rqspinlock.h
[ ... ]
> -#define smp_cond_load_acquire_timewait(ptr, cond_expr, \
> - time_expr_ns, time_limit_ns) \
> -({ \
> - __unqual_scalar_typeof(*ptr) _val; \
> - int __wfe = arch_timer_evtstrm_available(); \
> - \
> - if (likely(__wfe)) { \
> - _val = __smp_cond_load_acquire_timewait(ptr, cond_expr, \
> - time_expr_ns, \
> - time_limit_ns); \
> - } else { \
> - _val = __smp_cond_load_relaxed_spinwait(ptr, cond_expr, \
> - time_expr_ns, \
> - time_limit_ns); \
> - smp_acquire__after_ctrl_dep(); \
> - } \
> - (typeof(*ptr))_val; \
> -})
> -
> -#endif
> -
> -#define res_smp_cond_load_acquire(v, c) smp_cond_load_acquire_timewait(v, c, 0, 1)
[Severity: High]
With this custom fallback removed, the BPF rqspinlock code will use the generic
smp_cond_load_acquire(). Does this mean on platforms without a timer event
stream (arch_timer_evtstrm_available() is false), a CPU could get permanently
stuck in a WFE instruction during a lock timeout?
In kernel/bpf/rqspinlock.c:resilient_queued_spin_lock_slowpath(), the timeout is
evaluated as part of the condition expression:
res_smp_cond_load_acquire(&lock->locked, !VAL || RES_CHECK_TIMEOUT(ts, ret, _Q_LOCKED_MASK));
But smp_cond_load_acquire() calls __cmpwait_relaxed() which executes WFE:
__cmpwait_relaxed(__PTR, VAL);
If no stores occur to the locked byte, WFE will wait indefinitely, and the
embedded timeout check won't be evaluated while the CPU is asleep.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260714073041.40250-1-ankur.a.arora@oracle.com?part=5
next prev parent reply other threads:[~2026-07-14 7:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 7:30 [PATCH v14 00/15] barrier: Add smp_cond_load_{relaxed,acquire}_timeout() Ankur Arora
2026-07-14 7:30 ` [PATCH v14 01/15] asm-generic: barrier: Add smp_cond_load_relaxed_timeout() Ankur Arora
2026-07-14 7:42 ` sashiko-bot
2026-07-14 8:11 ` bot+bpf-ci
2026-07-14 7:30 ` [PATCH v14 02/15] arm64: barrier: Support smp_cond_load_relaxed_timeout() Ankur Arora
2026-07-14 7:50 ` sashiko-bot
2026-07-14 7:30 ` [PATCH v14 03/15] arm64/delay: move some constants out to a separate header Ankur Arora
2026-07-14 7:30 ` [PATCH v14 04/15] arm64: support WFET in smp_cond_load_relaxed_timeout() Ankur Arora
2026-07-14 7:53 ` sashiko-bot
2026-07-14 7:30 ` [PATCH v14 05/15] arm64: rqspinlock: Remove private copy of smp_cond_load_acquire_timewait() Ankur Arora
2026-07-14 7:44 ` sashiko-bot [this message]
2026-07-14 7:30 ` [PATCH v14 06/15] asm-generic: barrier: Add smp_cond_load_acquire_timeout() Ankur Arora
2026-07-14 7:53 ` sashiko-bot
2026-07-14 7:30 ` [PATCH v14 07/15] atomic: Add atomic_cond_read_*_timeout() Ankur Arora
2026-07-14 7:47 ` sashiko-bot
2026-07-14 7:30 ` [PATCH v14 08/15] locking/atomic: scripts: build atomic_long_cond_read_*_timeout() Ankur Arora
2026-07-14 7:30 ` [PATCH v14 09/15] bpf/rqspinlock: switch check_timeout() to a clock interface Ankur Arora
2026-07-14 7:30 ` [PATCH v14 10/15] bpf/rqspinlock: Use smp_cond_load_acquire_timeout() Ankur Arora
2026-07-14 8:11 ` bot+bpf-ci
2026-07-14 7:30 ` [PATCH v14 11/15] sched: add need-resched timed wait interface Ankur Arora
2026-07-14 7:30 ` [PATCH v14 12/15] cpuidle/poll_state: Wait for need-resched via tif_need_resched_relaxed_wait() Ankur Arora
2026-07-14 8:11 ` bot+bpf-ci
2026-07-14 7:30 ` [PATCH v14 13/15] arm64/delay: enable testing smp_cond_load_relaxed_timeout() Ankur Arora
2026-07-14 7:58 ` sashiko-bot
2026-07-14 7:30 ` [PATCH v14 14/15] barrier: add tests for smp_cond_load_*_timeout() Ankur Arora
2026-07-14 7:55 ` sashiko-bot
2026-07-14 8:11 ` bot+bpf-ci
2026-07-14 7:30 ` [PATCH v14 15/15] barrier: add clock tests for smp_cond_load_relaxed_timeout() Ankur Arora
2026-07-14 8:03 ` sashiko-bot
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=20260714074406.95EDF1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=ankur.a.arora@oracle.com \
--cc=bpf@vger.kernel.org \
--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