From: sashiko-bot@kernel.org
To: "Ankur Arora" <ankur.a.arora@oracle.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH v15 13/16] arm64/delay: enable testing smp_cond_load_relaxed_timeout()
Date: Mon, 31 Aug 2026 23:28:52 +0000 [thread overview]
Message-ID: <20260831232853.24ECF1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260831202251.305046-14-ankur.a.arora@oracle.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Conditional export of symbols used by generic inline macros breaks standard module usage.
--
commit 062222b285463a87a0b87a1f19a5112a409a0599
Author: Ankur Arora <ankur.a.arora@oracle.com>
arm64/delay: enable testing smp_cond_load_relaxed_timeout()
This enables the barrier tests to be built as a module by exporting the
internal delay and timer functions for KUnit.
> 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]
Since smp_cond_load_relaxed_timeout() is an inline macro that expands to call
cpu_poll_relax() and __cmpwait_relaxed_timeout(), and those rely on
__delay_cycles(), does restricting this export to KUnit builds break standard
loadable modules?
If a standard kernel module (built without CONFIG_KUNIT) tries to use the
generic smp_cond_load_relaxed_timeout() API, it seems it will fail to link
with a modpost error because this mandatory symbol isn't exported. Would a
standard EXPORT_SYMBOL_GPL() be more appropriate here to ensure the generic
barrier API remains usable by all modules?
> diff --git a/drivers/clocksource/arm_arch_timer.c b/drivers/clocksource/arm_arch_timer.c
> index 4adf756423de9..91ab8552ead83 100644
> --- a/drivers/clocksource/arm_arch_timer.c
> +++ b/drivers/clocksource/arm_arch_timer.c
[ ... ]
> @@ -897,6 +898,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]
Similar to __delay_cycles() above, arch_timer_evtstrm_available() is called
by the inline expansion of smp_cond_load_relaxed_timeout(). Does this
conditional export render the generic synchronization API unusable for
non-KUnit modules that might want to use it?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260831202251.305046-1-ankur.a.arora@oracle.com?part=13
next prev parent reply other threads:[~2026-08-31 23:28 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 20:22 [PATCH v15 00/16] barrier: Add smp_cond_load_{relaxed,acquire}_timeout() Ankur Arora
2026-08-31 20:22 ` [PATCH v15 01/16] asm-generic: barrier: Add smp_cond_load_relaxed_timeout() Ankur Arora
2026-08-31 21:50 ` sashiko-bot
2026-08-31 20:22 ` [PATCH v15 02/16] arm64: barrier: Support smp_cond_load_relaxed_timeout() Ankur Arora
2026-08-31 21:59 ` sashiko-bot
2026-09-01 3:55 ` Ankur Arora
2026-08-31 20:22 ` [PATCH v15 03/16] arm64/delay: move, fixup usecs_to_cycles() Ankur Arora
2026-08-31 22:06 ` sashiko-bot
2026-08-31 20:22 ` [PATCH v15 04/16] arm64: support WFET in smp_cond_load_relaxed_timeout() Ankur Arora
2026-08-31 21:16 ` bot+bpf-ci
2026-08-31 22:19 ` sashiko-bot
2026-08-31 20:22 ` [PATCH v15 05/16] arm64: rqspinlock: Remove private copy of smp_cond_load_acquire_timewait() Ankur Arora
2026-08-31 20:22 ` [PATCH v15 06/16] asm-generic: barrier: Add smp_cond_load_acquire_timeout() Ankur Arora
2026-08-31 21:17 ` bot+bpf-ci
2026-08-31 22:36 ` sashiko-bot
2026-08-31 20:22 ` [PATCH v15 07/16] atomic: Add atomic_cond_read_*_timeout() Ankur Arora
2026-08-31 21:16 ` bot+bpf-ci
2026-08-31 22:47 ` sashiko-bot
2026-08-31 20:22 ` [PATCH v15 08/16] locking/atomic: scripts: build atomic_long_cond_read_*_timeout() Ankur Arora
2026-08-31 20:22 ` [PATCH v15 09/16] bpf/rqspinlock: switch check_timeout() to a clock interface Ankur Arora
2026-08-31 21:16 ` bot+bpf-ci
2026-08-31 20:22 ` [PATCH v15 10/16] bpf/rqspinlock: Use smp_cond_load_acquire_timeout() Ankur Arora
2026-08-31 21:31 ` bot+bpf-ci
2026-08-31 20:22 ` [PATCH v15 11/16] sched: add need-resched timed wait interface Ankur Arora
2026-08-31 20:22 ` [PATCH v15 12/16] cpuidle/poll_state: Wait for need-resched via tif_need_resched_relaxed_wait() Ankur Arora
2026-08-31 23:20 ` sashiko-bot
2026-09-01 4:46 ` Ankur Arora
2026-09-10 23:04 ` Haris Okanovic
2026-09-11 7:13 ` Ankur Arora
2026-08-31 20:22 ` [PATCH v15 13/16] arm64/delay: enable testing smp_cond_load_relaxed_timeout() Ankur Arora
2026-08-31 21:16 ` bot+bpf-ci
2026-08-31 23:28 ` sashiko-bot [this message]
2026-09-01 4:53 ` Ankur Arora
2026-08-31 20:22 ` [PATCH v15 14/16] barrier: add tests for smp_cond_load_*_timeout() Ankur Arora
2026-08-31 21:17 ` bot+bpf-ci
2026-09-10 23:04 ` Haris Okanovic
2026-08-31 20:22 ` [PATCH v15 15/16] barrier: timeout validity checks for smp_cond_load_relaxed_timeout() Ankur Arora
2026-08-31 21:16 ` bot+bpf-ci
2026-09-10 23:04 ` Haris Okanovic
2026-08-31 20:22 ` [PATCH v15 16/16] barrier: timeout validity checks for smp_cond_load_acquire_timeout() Ankur Arora
2026-09-10 23:04 ` Haris Okanovic
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=20260831232853.24ECF1F000E9@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 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.