public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Matthew Maurer <mmaurer@google.com>,
	Alice Ryhl <aliceryhl@google.com>,
	Sami Tolvanen <samitolvanen@google.com>,
	Gatlin Newhouse <gatlin.newhouse@gmail.com>,
	Kees Cook <kees@kernel.org>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Miguel Ojeda <ojeda@kernel.org>,
	Andrey Konovalov <andreyknvl@gmail.com>,
	Marco Elver <elver@google.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of Linus' tree
Date: Thu, 26 Sep 2024 10:04:34 +1000	[thread overview]
Message-ID: <20240926100434.45d58861@canb.auug.org.au> (raw)

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

Hi all,

After merging Linus' tree, today's linux-next build (x86_64
allmodconfig) failed (very quickly) like this:

error: unknown unstable option: `patchable-function-entry`

Presumably exposed by commit

  1f9c4a996756 ("Kbuild: make MODVERSIONS support depend on not being a compile test build")

Which allowed the rust parts of the build to happen in my x86_64
allmodconfig build.

This is a cross build on a PowerPC LE host.

$ rustc --version
rustc 1.80.1
$ x86_64-linux-gnu-gcc --version
x86_64-linux-gnu-gcc (Debian 14.2.0-1) 14.2.0

I have reverted these commits for today:

  a2f115470520 ("kasan: rust: Add KASAN smoke test via UAF")
  e3117404b411 ("kbuild: rust: Enable KASAN support")
  f64e2f3a66e3 ("rust: kasan: Rust does not support KHWASAN")
  c42297438aee ("kbuild: rust: Define probing macros for rustc")
  cc1d98f9fe30 ("kasan: simplify and clarify Makefile")
  ca627e636551 ("rust: cfi: add support for CFI_CLANG with Rust")

Basically for the latter one (as a guess).

And the build works.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-09-26  0:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26  0:04 Stephen Rothwell [this message]
2024-09-26  7:36 ` linux-next: build failure after merge of Linus' tree Alice Ryhl
2024-09-26  8:13   ` Stephen Rothwell
2024-09-26  8:24     ` Miguel Ojeda
2024-09-26 12:49       ` Sedat Dilek
2024-09-26 12:58         ` Miguel Ojeda
2024-09-26 14:44           ` Sedat Dilek
2024-09-26 14:57             ` Miguel Ojeda
  -- strict thread matches above, loose matches on Subject: below --
2025-02-03  1:59 Stephen Rothwell
2025-02-03  2:56 ` Jens Axboe
2020-04-20 11:35 Stephen Rothwell
2016-08-08  1:58 Stephen Rothwell
2016-08-08 15:37 ` Doug Ledford
2016-08-08 21:53   ` Stephen Rothwell
2016-08-08 23:30     ` Doug Ledford
2016-08-08 23:59       ` Stephen Rothwell
2016-08-09  8:54   ` Leon Romanovsky
2016-08-09 12:45     ` Doug Ledford
2015-10-07 22:44 Stephen Rothwell

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=20240926100434.45d58861@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=aliceryhl@google.com \
    --cc=andreyknvl@gmail.com \
    --cc=elver@google.com \
    --cc=gatlin.newhouse@gmail.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mmaurer@google.com \
    --cc=ojeda@kernel.org \
    --cc=peterz@infradead.org \
    --cc=samitolvanen@google.com \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox