From: Kees Cook <[email protected]>
To: kernel test robot <[email protected]>,
Andrew Morton <[email protected]>
Cc: Linux Memory Management List <[email protected]>,
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
John Paul Adrian Glaubitz <[email protected]>
Subject: Re: [linux-next:master] BUILD REGRESSION e31185ce00a96232308300008db193416ceb9769
Date: Fri, 23 Feb 2024 07:46:40 -0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On February 22, 2024 8:29:28 PM PST, kernel test robot <[email protected]> wrote:
>tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>branch HEAD: e31185ce00a96232308300008db193416ceb9769 Add linux-next specific files for 20240222
>
>Error/Warning reports:
>
>https://lore.kernel.org/oe-kbuild-all/[email protected]
>https://lore.kernel.org/oe-kbuild-all/[email protected]
>https://lore.kernel.org/oe-kbuild-all/[email protected]
>
>Error/Warning: (recently discovered and may have been fixed)
>
>arch/arm/boot/compressed/misc.c:157:6: warning: no previous prototype for function '__fortify_panic' [-Wmissing-prototypes]
>arch/arm/boot/compressed/misc.h:13:36: error: macro "fortify_panic" requires 2 arguments, but only 1 given
This is fixed for the subsequent -next tree.
>arch/sh/boot/compressed/../../../../lib/decompress_unxz.c:350:(.text+0x20b4): undefined reference to `__ubsan_handle_out_of_bounds'
>sh4-linux-ld: arch/sh/boot/compressed/../../../../lib/xz/xz_dec_lzma2.c:751:(.text+0x904): undefined reference to `__ubsan_handle_out_of_bounds'
This is fixed here and is waiting to land:
https://lore.kernel.org/linux-hardening/[email protected]/
-Kees
--
Kees Cook
next prev parent reply other threads:[~2024-02-23 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 4:29 [linux-next:master] BUILD REGRESSION e31185ce00a96232308300008db193416ceb9769 kernel test robot
2024-02-23 15:46 ` Kees Cook [this message]
2024-02-23 16:04 ` John Paul Adrian Glaubitz
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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