From: Kees Cook <keescook@chromium.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Sebastian Ott <sebott@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the execve tree
Date: Tue, 3 Oct 2023 19:50:28 -0700 [thread overview]
Message-ID: <202310031950.E698038489@keescook> (raw)
In-Reply-To: <20231003133522.310bda60@canb.auug.org.au>
On Tue, Oct 03, 2023 at 01:35:22PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the execve tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> fs/binfmt_elf.c: In function 'load_elf_library':
> fs/binfmt_elf.c:1323:37: error: unused variable 'len' [-Werror=unused-variable]
> 1323 | unsigned long elf_bss, bss, len;
> | ^~~
> fs/binfmt_elf.c:1323:32: error: unused variable 'bss' [-Werror=unused-variable]
> 1323 | unsigned long elf_bss, bss, len;
> | ^~~
> fs/binfmt_elf.c:1323:23: error: unused variable 'elf_bss' [-Werror=unused-variable]
> 1323 | unsigned long elf_bss, bss, len;
> | ^~~~~~~
> cc1: all warnings being treated as errors
>
> Caused by commit
>
> f2a1e5fab9ae ("binfmt_elf: Use elf_load() for library")
>
> I have used the execve tree from next-20230929 for today.
Whoops! Fixed now. Thanks. :)
--
Kees Cook
next prev parent reply other threads:[~2023-10-04 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 2:35 linux-next: build failure after merge of the execve tree Stephen Rothwell
2023-10-04 2:50 ` Kees Cook [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-24 6:40 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=202310031950.E698038489@keescook \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sebott@redhat.com \
--cc=sfr@canb.auug.org.au \
/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