From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Thierry Reding" <thierry.reding@kernel.org>
Cc: "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 efi-fixes tree
Date: Tue, 28 Apr 2026 12:25:07 +0200 [thread overview]
Message-ID: <69bfbb1f-8817-44f8-afe8-5eb04094f634@app.fastmail.com> (raw)
In-Reply-To: <20260428102251.3877875-1-thierry.reding@kernel.org>
Hi Thierry,
On Tue, 28 Apr 2026, at 12:22, Thierry Reding wrote:
> Hi all,
>
> After merging the efi-fixes tree, today's linux-next build (all of them)
> failed like this:
>
> /srv/kbuild/next/linux.git/fs/efivarfs/super.c: In function
> 'efivarfs_d_hash':
> /srv/kbuild/next/linux.git/fs/efivarfs/super.c:183:20: error:
> assignment of member 'hash' in read-only object
> 183 | qstr->hash = end_name_hash(hash);
> | ^
> /srv/kbuild/next/linux.git/fs/efivarfs/super.c: At top level:
> /srv/kbuild/next/linux.git/fs/efivarfs/super.c:189:19: error:
> initialization of 'int (*)(const struct dentry *, struct qstr *)' from
> incompatible pointer type 'int (*)(const struct dentry *, const struct
> qstr *)' [-Wincompatible-pointer-types]
> 189 | .d_hash = efivarfs_d_hash,
> | ^~~~~~~~~~~~~~~
> Caused by commit
>
> 9c7c5eec5bca ("efivarfs: use QSTR() in efivarfs_alloc_dentry")
>
> and like this:
>
> arm-linux-gnueabihf-ld:
> drivers/firmware/efi/libstub/relocate.stub.o: in function
> `efi_relocate_kernel':
>
> /srv/kbuild/next/linux.git/drivers/firmware/efi/libstub/relocate.c:161:(.text+0x278):
> undefined reference to `efi_cache_sync_image'
> arm-linux-gnueabihf-ld: arch/arm/boot/compressed/vmlinux: hidden
> symbol `efi_cache_sync_image' isn't defined
> arm-linux-gnueabihf-ld: final link failed: bad value
>
> Caused by commit
>
> 4db2b7fdd6c9 ("efi/libstub: Synchronize instruction cache after
> kernel relocation")
>
> I've fixed up both issues with the following patches, please squash these
> or equivalent changes into your tree to fix this.
>
Apologies for the breakage.
I'll drop these for now.
next prev parent reply other threads:[~2026-04-28 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 10:22 Thierry Reding
2026-04-28 10:25 ` Ard Biesheuvel [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-13 22:40 Stephen Rothwell
2023-03-13 23:06 ` Ard Biesheuvel
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=69bfbb1f-8817-44f8-afe8-5eb04094f634@app.fastmail.com \
--to=ardb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=thierry.reding@kernel.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
all inboxes | Powered by JetHome®