Re: linux-next: build failure after merge of the tip tree

Peter Zijlstra
2024-11-07T08:40:38Z

[-- Attachment #1: Type: text/plain, Size: 2015 bytes --]

On Thu, Nov 07, 2024 at 06:24:11PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> In file included from rust/helpers/helpers.c:26:
> rust/helpers/spinlock.c: In function 'rust_helper___spin_lock_init':
> rust/helpers/spinlock.c:10:30: error: implicit declaration of function 'spinlock_check'; did you mean 'spin_lock_bh'? [-Wimplicit-function-declaration]
> 10 | __raw_spin_lock_init(spinlock_check(lock), name, key, LD_WAIT_CONFIG);
> | ^~~~~~~~~~~~~~
> | spin_lock_bh
> rust/helpers/spinlock.c:10:30: error: passing argument 1 of '__raw_spin_lock_init' makes pointer from integer without a cast [-Wint-conversion]
> 10 | __raw_spin_lock_init(spinlock_check(lock), name, key, LD_WAIT_CONFIG);
> | ^~~~~~~~~~~~~~~~~~~~
> | |
> | int
> In file included from include/linux/wait.h:9,
> from include/linux/wait_bit.h:8,
> from include/linux/fs.h:6,
> from include/linux/highmem.h:5,
> from include/linux/bvec.h:10,
> from include/linux/blk_types.h:10,
> from include/linux/blkdev.h:9,
> from include/linux/blk-mq.h:5,
> from rust/helpers/blk.c:3,
> from rust/helpers/helpers.c:10:
> include/linux/spinlock.h:101:52: note: expected 'raw_spinlock_t *' {aka 'struct raw_spinlock *'} but argument is of type 'int'
> 101 | extern void __raw_spin_lock_init(raw_spinlock_t *lock, const char *name,
> | ~~~~~~~~~~~~~~~~^~~~
>

Urgh, these commits have been exposed to the build robot for weeks :-(

Oh well, let met go figure out how to build this rust crap again and see
what's what.

Thanks!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]