All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Christian Heusel <christian@heusel.eu>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
	rust-for-linux@vger.kernel.org,
	open list <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	lkft-triage@lists.linaro.org, 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>,
	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: Wed, 17 Sep 2025 10:42:35 +0300	[thread overview]
Message-ID: <aMpma-2UokTo0u9j@stanley.mountain> (raw)
In-Reply-To: <27366f94-67d4-4b73-b420-cacdbe9d603f@heusel.eu>

On Tue, Sep 16, 2025 at 06:46:06PM +0200, Christian Heusel wrote:
> On 25/09/16 09:56PM, Naresh Kamboju wrote:
> > 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
> 
> Is this still an issue on next-20250916? As far as I can tell this has
> been fixed, but now there is another rust build issue, see
> https://lore.kernel.org/regressions/0fee48bb-7411-4414-b4e7-395a8c3d0f6c@heusel.eu/
> for more information.
> 
> Cheers,
> Chris
> 

next-20250916 still fails but with a different Rust issue.

$ make
  SYNC    include/config/auto.conf
  HOSTCC  scripts/basic/fixdep
  CALL    scripts/checksyscalls.sh
  DESCEND objtool
  INSTALL libsubcmd_headers
  RUSTC L rust/kernel.o
error: expected one of `,` or `}`, found `;`
  --> rust/kernel/block/mq/gen_disk.rs:12:23
   |
12 |     fmt::{self, Write};
   |                       ^
   |                       |
   |                       expected one of `,` or `}`
   |                       help: missing `,`

error: aborting due to 1 previous error

make[2]: *** [rust/Makefile:553: rust/kernel.o] Error 1
make[1]: *** [/home/dcarpenter/progs/kernel/devel/Makefile:1286: prepare] Error 2
make: *** [Makefile:248: __sub-make] Error 2

regards,
dan carpenter


  reply	other threads:[~2025-09-17  7:42 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
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 [this message]
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=aMpma-2UokTo0u9j@stanley.mountain \
    --to=dan.carpenter@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=christian@heusel.eu \
    --cc=elle@weathered-steel.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=lossin@kernel.org \
    --cc=naresh.kamboju@linaro.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 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.