From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: rust-for-linux@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
lkft-triage@lists.linaro.org
Cc: Miguel Ojeda <ojeda@kernel.org>,
Alex Gaynor <alex.gaynor@gmail.com>,
Boqun Feng <boqun.feng@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Alice Ryhl <aliceryhl@google.com>,
Benno Lossin <lossin@kernel.org>,
Elle Rhumsaa <elle@weathered-steel.dev>,
Dan Carpenter <dan.carpenter@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>,
Ben Copeland <benjamin.copeland@linaro.org>
Subject: Re: next-20250915: error[E0425]: cannot find function `atomic_read_acquire` in crate `bindings`
Date: Tue, 16 Sep 2025 21:56:38 +0530 [thread overview]
Message-ID: <CA+G9fYs4JB0ngq+aryXHVQSq-f05cb4agCfyM9zN0SgprQf0_A@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYtT7HNBM2XBbePeZ-Fw+ig7SJ+JE_NpQ1VuHR_TvAjX2w@mail.gmail.com>
On Tue, 16 Sept 2025 at 11:17, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> The following build warnings / errors noticed on the arm arm64 and x86_64
> with rust config build on the Linux next-20250915 tag.
>
> First seen on next-20250915
> Good: next-20250912
> Bad: next-20250915
>
> Regression Analysis:
> - New regression? yes
> - Reproducibility? yes
>
> * arm, build
> - rustclang-lkftconfig-kselftest
> - rustgcc-lkftconfig-kselftest
>
> * arm64, build
> - rustclang-lkftconfig-kselftest
> - rustgcc-lkftconfig-kselftest
>
> * x86_64, build
> - rustgcc-lkftconfig-kselftest
> - rustclang-nightly-lkftconfig-kselftest
>
> Build regression: next-20250915: error[E0425]: cannot find function
> `atomic_read_acquire` in crate `bindings`
Anders bisected this build regressions and found,
# first bad commit:
[eb57133305f61b612252382d0c1478bba7f57b67]
rust: sync: Add basic atomic operation mapping framework
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> ## Build log
> error[E0425]: cannot find function `atomic_read_acquire` in crate `bindings`
> --> rust/kernel/sync/atomic/internal.rs:124:37
> |
> 124 | $unsafe { bindings::[< $ctype _ $func >]($($c_arg,)*) }
> | ^^^^^^^^^^^^^^^^^^^^ not
> found in `bindings`
> ...
> 201 | / declare_and_impl_atomic_methods!(
> 202 | | /// Basic atomic operations
> 203 | | pub trait AtomicBasicOps {
> 204 | | /// Atomic read (load).
> ... |
> 216 | | );
> | |_- in this macro invocation
> |
> = note: this error originates in the macro `impl_atomic_method`
> which comes from the expansion of the macro
> `declare_and_impl_atomic_methods` (in Nightly builds, run with -Z
> macro-backtrace for more info)
> error: aborting due to 34 previous errors
>
> For more information about this error, try `rustc --explain E0425`.
> make[3]: *** [rust/Makefile:553: rust/kernel.o] Error 1
>
>
> ## Source
> * Kernel version: 6.17.0-rc6
> * Git tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git
> * Git describe: 6.17.0-rc6-next-20250915
> * Git commit: c3067c2c38316c3ef013636c93daa285ee6aaa2e
> * Architectures: arm, arm64 and x86_64
> * Toolchains: gcc (Debian 15.2.0-3) 15.2.0
> * Kconfigs: rust config
>
> ## Build
> * Build log: https://qa-reports.linaro.org/api/testruns/29894207/log_file/
> * Build details:
> https://regressions.linaro.org/lkft/linux-next-master/next-20250915/build/rustgcc-lkftconfig-kselftest/
> * Build plan: https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/builds/32l4UDzp0FMtS73JeG3kWpcoQrm
> * Build link: https://storage.tuxsuite.com/public/linaro/lkft/builds/32l4UDzp0FMtS73JeG3kWpcoQrm/
> * Kernel config:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/32l4UDzp0FMtS73JeG3kWpcoQrm/config
>
> --
> Linaro LKFT
- Naresh
next prev parent reply other threads:[~2025-09-16 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 5:47 next-20250915: error[E0425]: cannot find function `atomic_read_acquire` in crate `bindings` Naresh Kamboju
2025-09-16 16:26 ` Naresh Kamboju [this message]
2025-09-16 16:40 ` Miguel Ojeda
2025-09-16 17:40 ` Boqun Feng
2025-09-16 16:46 ` Christian Heusel
2025-09-17 7:42 ` Dan Carpenter
2025-09-17 7:58 ` Thorsten Leemhuis
2025-09-17 16:30 ` Christian Heusel
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=CA+G9fYs4JB0ngq+aryXHVQSq-f05cb4agCfyM9zN0SgprQf0_A@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=benjamin.copeland@linaro.org \
--cc=boqun.feng@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=elle@weathered-steel.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=regressions@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).