Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20220919191126.4a3c36f9@canb.auug.org.au> <CAMj1kXFKm2A=zNHRSWtWkwBXWM=tQD=x+Q6-Mv_a66qopiXkjQ@mail.gmail.com>
In-Reply-To: <CAMj1kXFKm2A=zNHRSWtWkwBXWM=tQD=x+Q6-Mv_a66qopiXkjQ@mail.gmail.com>
From:   Ard Biesheuvel <ardb@kernel.org>
Date:   Mon, 19 Sep 2022 11:25:10 +0200
Message-ID: <CAMj1kXHsAbn2NtJaT8F0evMd19w4nJON+TXV62k2Jsj+o+LTCA@mail.gmail.com>
Subject: Re: linux-next: build failure after merge of the efi tree
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Mon, 19 Sept 2022 at 11:12, Ard Biesheuvel <ardb@kernel.org> wrote:
>
> On Mon, 19 Sept 2022 at 11:11, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Hi all,
> >
> > After merging the efi tree, today's linux-next build (x86_64 allmodconfig)
> > failed like this:
> >
> > x86_64-linux-gnu-ld: drivers/firmware/efi/libstub/x86-stub.stub.o:(.bss.efistub+0x8): multiple definition of `efi_system_table'; drivers/firmware/efi/libstub/systable.stub.o:(.bss.efistub+0x0): first defined here
> >
> > Presumably caused by commit
> >
> >   8fd3c9a90998 ("efi/libstub: move efi_system_table global var into separate object")
> >
> > (or maybe commit
> >
> >   ba2dd31b7588 ("efi/libstub: implement generic EFI zboot")
> > )
> >
> > I have used the efi tree from next-20220916 for today.
> >
>
> Thanks for the report. I'll take a look and fix this asap.

Fixed now on efi/next so we should be ok for tomorrow.