linux-kernel - Re: [GIT PULL] MM updates for 6.14-rc1

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20250125210016.815b4260ad539b1e66298d98@linux-foundation.org>
Date: Sat, 25 Jan 2025 21:00:16 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Uros Bizjak <ubizjak@...il.com>, linux-mm@...ck.org,
 mm-commits@...r.kernel.org, linux-kernel@...r.kernel.org, Stephen Rothwell
 <sfr@...b.auug.org.au>, Dan Carpenter <dan.carpenter@...aro.org>, Anders
 Roxell <anders.roxell@...aro.org>, Naresh Kamboju
 <naresh.kamboju@...aro.org>
Subject: Re: [GIT PULL] MM updates for 6.14-rc1

On Sat, 25 Jan 2025 14:09:16 -0800 Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Fri, 24 Jan 2025 at 16:22, Andrew Morton <akpm@...ux-foundation.org> wrote:
> >
> > Linus, please merge the MM updates for the 6.14 development cycle,
> 
> This does not build at all for me.
> 
> I get
> 
>     ./arch/x86/include/asm/current.h:49:9: error: call to undeclared
> function '__typeof_unqual__'; ISO C99 and later do not support
> implicit function declarations [-Wimplicit-function-declaration]
> 
> when running the Rust 'bindgen', and what seems to be going on is that
> my version of *gcc* does support __typeof_unqual__, so I end up with
> 
>     CONFIG_CC_HAS_TYPEOF_UNQUAL=y
> 
> in my kernel config, but I think that 'bindgen' that generates the
> Rust bindings is based on LLVM, and clearly does not understand
> __typeof_unqual__.
> 
> I have bindgen 0.69.5 (plain F40 install), in case somebody wants to test.
> 
> Apparently few people test linux-next with Rust enabled, and the
> reports that I find on lkml were ignored.
>
> I do see reports of this failure on lkml from mid-December, so it's
> not like I'm the first person ever to see this.
> 

Well dang, nobody told me, and I assume Stephen didn't find out.

Guys, if tree owners are carrying bad patches, please do give them a
heads-up!

> Anyway, pulled and then unpulled again.

OK, I've dropped Uroz's series "Enable strict percpu address space
checks", shall resend the pull request soon.

And I shall continue to scratch my head over
Documentation/rust/quick-start.rst.