linux-kernel - Re: rustgcc-kselftest: error: unknown unstable option: `patchable-function-entry`

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: <CANiq72kaAd5v+c+A3GHWp9riDtGTrKcCb3kraw2EaZLyp8asSg@mail.gmail.com>
Date: Mon, 16 Sep 2024 21:23:28 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: rust-for-linux@...r.kernel.org, open list <linux-kernel@...r.kernel.org>, 
	"open list:KERNEL SELFTEST FRAMEWORK" <linux-kselftest@...r.kernel.org>, lkft-triage@...ts.linaro.org, 
	Linux Regressions <regressions@...ts.linux.dev>, Miguel Ojeda <ojeda@...nel.org>, aliceryhl@...gle.com, 
	Shuah Khan <shuah@...nel.org>, Arnd Bergmann <arnd@...db.de>, 
	Dan Carpenter <dan.carpenter@...aro.org>, Anders Roxell <anders.roxell@...aro.org>
Subject: Re: rustgcc-kselftest: error: unknown unstable option: `patchable-function-entry`

Hi Naresh,

On Mon, Sep 16, 2024 at 9:17 PM Naresh Kamboju
<naresh.kamboju@...aro.org> wrote:
>
> The x86 rust gcc builds failed on the Linux next-20240917 due to following build
> warnings / errors with rustgcc for selftests rust builds.
>
> First seen on next-20240917
>   Good: next-20240913
>   BAD:  next-20240917
>
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>

Thanks for the report -- this should be already fixed in `rust-next`
for tomorrow (requirement changed from `!FINEIBT` to `!CALL_PADDING`),
please see https://lore.kernel.org/rust-for-linux/CANiq72=B9NmC=1eSaOrg7XutjueQsSXGcBQb7dQFPuL0SFjPsA@mail.gmail.com/

If you can confirm it is, that would be great, thanks! i.e. you will
need either to disable `CALL_PADDING` or use a newer Rust compiler
version.

By the way, I think you meant next-202409176, not next-20240917?

Cheers,
Miguel