From: sashiko-bot@kernel.org
To: "Ankur Arora" <ankur.a.arora@oracle.com>, bpf@vger.kernel.org
Subject: Re: [PATCH v16 13/16] arm64/delay: enable testing smp_cond_load_relaxed_timeout()
Date: Fri, 16 Oct 2026 07:20:09 +0000 [thread overview]
Message-ID: <sashiko-outbox-173916@kernel.org> (raw)
In-Reply-To: <20261016070837.440748-14-ankur.a.arora@oracle.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] arm64: barrier: missing exports for smp_cond_load_*_timeout() backends
--
commit bfc8166431acdeebcd1866a53cbd230aa1bcd738
Author: Ankur Arora <ankur.a.arora@oracle.com>
arm64/delay: enable testing smp_cond_load_relaxed_timeout()
This commit enables the barrier tests to be built as a module by exporting
the underlying delay and timer functions when KUnit is enabled.
> diff --git a/arch/arm64/lib/delay.c b/arch/arm64/lib/delay.c
> index f08eacef2f0a4..20bc2894b65b9 100644
> --- a/arch/arm64/lib/delay.c
> +++ b/arch/arm64/lib/delay.c
[ ... ]
> @@ -30,6 +31,7 @@ u64 notrace __delay_cycles(void)
> guard(preempt_notrace)();
> return __arch_counter_get_cntvct_stable();
> }
> +EXPORT_SYMBOL_IF_KUNIT(__delay_cycles);
[Severity: Medium]
Does exporting __delay_cycles() only for KUnit cause unresolved symbol errors
for standard loadable modules?
If a standard non-test module uses atomic_cond_read_acquire_timeout() or
smp_cond_load_relaxed_timeout() on ARM64, the macros expand to inline barrier
functions like __cmpwait_relaxed_timeout(), which call __delay_cycles().
Since this symbol is only exported when CONFIG_KUNIT is enabled, will standard
production builds fail to build or load modules using these APIs?
>
> void __delay(unsigned long cycles)
> diff --git a/drivers/clocksource/arm_arch_timer.c b/drivers/clocksource/arm_arch_timer.c
> index cc9a8b399004d..227447b19b143 100644
> --- a/drivers/clocksource/arm_arch_timer.c
> +++ b/drivers/clocksource/arm_arch_timer.c
[ ... ]
> @@ -893,6 +894,7 @@ bool arch_timer_evtstrm_available(void)
> */
> return cpumask_test_cpu(raw_smp_processor_id(), &evtstrm_available);
> }
> +EXPORT_SYMBOL_IF_KUNIT(arch_timer_evtstrm_available);
[Severity: Medium]
Similarly, does restricting the export of arch_timer_evtstrm_available() to
KUnit builds break standard modules?
The inline cpu_poll_relax() backend relies on this function. Standard modules
using the new timeout APIs might fail to resolve this symbol when compiled
without CONFIG_KUNIT. Should these be exported unconditionally using standard
EXPORT_SYMBOL_GPL() instead?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261016070837.440748-1-ankur.a.arora@oracle.com?part=13
next prev parent reply other threads:[~2026-10-16 7:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 7:08 [PATCH v16 00/16] barrier: Add smp_cond_load_{relaxed,acquire}_timeout() Ankur Arora
2026-10-16 7:08 ` [PATCH v16 01/16] asm-generic: barrier: Add smp_cond_load_relaxed_timeout() Ankur Arora
2026-10-16 7:21 ` sashiko-bot
2026-10-16 7:55 ` bot+bpf-ci
2026-10-16 7:08 ` [PATCH v16 02/16] arm64: barrier: Support smp_cond_load_relaxed_timeout() Ankur Arora
2026-10-16 7:24 ` sashiko-bot
2026-10-16 7:08 ` [PATCH v16 03/16] arm64/delay: move, fixup usecs_to_cycles() Ankur Arora
2026-10-16 7:16 ` sashiko-bot
2026-10-16 7:55 ` bot+bpf-ci
2026-10-16 12:22 ` Catalin Marinas
2026-10-16 7:08 ` [PATCH v16 04/16] arm64: support WFET in smp_cond_load_relaxed_timeout() Ankur Arora
2026-10-16 7:27 ` sashiko-bot
2026-10-16 7:55 ` bot+bpf-ci
2026-10-16 7:08 ` [PATCH v16 05/16] arm64: rqspinlock: Remove private copy of smp_cond_load_acquire_timewait() Ankur Arora
2026-10-16 7:08 ` [PATCH v16 06/16] asm-generic: barrier: Add smp_cond_load_acquire_timeout() Ankur Arora
2026-10-16 7:21 ` sashiko-bot
2026-10-16 7:08 ` [PATCH v16 07/16] atomic: Add atomic_cond_read_*_timeout() Ankur Arora
2026-10-16 7:25 ` sashiko-bot
2026-10-16 7:08 ` [PATCH v16 08/16] locking/atomic: scripts: build atomic_long_cond_read_*_timeout() Ankur Arora
2026-10-16 7:08 ` [PATCH v16 09/16] bpf/rqspinlock: switch check_timeout() to a clock interface Ankur Arora
2026-10-16 7:08 ` [PATCH v16 10/16] bpf/rqspinlock: Use smp_cond_load_acquire_timeout() Ankur Arora
2026-10-16 7:08 ` [PATCH v16 11/16] sched: add need-resched timed wait interface Ankur Arora
2026-10-16 7:08 ` [PATCH v16 12/16] cpuidle/poll_state: Wait for need-resched via tif_need_resched_relaxed_wait() Ankur Arora
2026-10-16 7:08 ` [PATCH v16 13/16] arm64/delay: enable testing smp_cond_load_relaxed_timeout() Ankur Arora
2026-10-16 7:20 ` sashiko-bot [this message]
2026-10-16 7:08 ` [PATCH v16 14/16] barrier: add tests for smp_cond_load_*_timeout() Ankur Arora
2026-10-16 7:55 ` bot+bpf-ci
2026-10-16 7:08 ` [PATCH v16 15/16] barrier: timeout validity checks for smp_cond_load_relaxed_timeout() Ankur Arora
2026-10-16 7:19 ` sashiko-bot
2026-10-16 7:55 ` bot+bpf-ci
2026-10-16 7:08 ` [PATCH v16 16/16] barrier: timeout validity checks for smp_cond_load_acquire_timeout() Ankur Arora
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=sashiko-outbox-173916@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 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.