linux-kernel - linux-next: build failure after merge of the kvm tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250528152832.3ce43330@canb.auug.org.au>
Date: Wed, 28 May 2025 15:28:32 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: Maxim Levitsky <mlevitsk@...hat.com>, KVM <kvm@...r.kernel.org>, Linux
 Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next Mailing List
 <linux-next@...r.kernel.org>
Subject: linux-next: build failure after merge of the kvm tree

Hi all,

After merging the kvm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:

error[E0425]: cannot find function `mutex_trylock` in crate `bindings`
   --> rust/kernel/sync/lock/mutex.rs:129:41
    |
129 |         let result = unsafe { bindings::mutex_trylock(ptr) };
    |                                         ^^^^^^^^^^^^^ help: a function with a similar name exists: `mutex_lock`
    |
   ::: /home/sfr/next/x86_64_allmodconfig/rust/bindings/bindings_helpers_generated.rs:265:5
    |
265 |     pub fn mutex_lock(lock: *mut mutex);
    |     ------------------------------------ similarly named function `mutex_lock` defined here

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0425`.

Caused by commit

  c5b6ababd21a ("locking/mutex: implement mutex_trylock_nested")

I have used the kvm tree from next-20250527 for today.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped