[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMj1kXHc0uzzTKp7oj23_=X9ek2KNrKMq1gL09X7cTnjhV=nXQ@mail.gmail.com>
Date: Thu, 30 Apr 2020 23:25:53 +0200
From: Ard Biesheuvel <ardb@...nel.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: Jerry Snitselaar <jsnitsel@...hat.com>,
Ingo Molnar <mingo@...nel.org>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Ben Dooks <ben.dooks@...ethink.co.uk>,
Dave Young <dyoung@...hat.com>,
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
Lukas Wunner <lukas@...ner.de>, Lyude Paul <lyude@...hat.com>,
Matthew Garrett <mjg59@...gle.com>,
Octavian Purdila <octavian.purdila@...el.com>,
Peter Jones <pjones@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Scott Talbert <swt@...hie.net>,
Thomas Gleixner <tglx@...utronix.de>,
linux-efi <linux-efi@...r.kernel.org>,
linux-integrity@...r.kernel.org,
"# 3.4.x" <stable@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] efi/tpm: fix section mismatch warning
On Thu, 30 Apr 2020 at 23:21, Arnd Bergmann <arnd@...db.de> wrote:
>
> On Thu, Apr 30, 2020 at 11:15 PM Jerry Snitselaar <jsnitsel@...hat.com> wrote:
> >
> > On Wed Apr 29 20, Arnd Bergmann wrote:
> > >Building with gcc-10 causes a harmless warning about a section mismatch:
> > >
> > >WARNING: modpost: vmlinux.o(.text.unlikely+0x5e191): Section mismatch in reference from the function tpm2_calc_event_log_size() to the function .init.text:early_memunmap()
> > >The function tpm2_calc_event_log_size() references
> > >the function __init early_memunmap().
> > >This is often because tpm2_calc_event_log_size lacks a __init
> > >annotation or the annotation of early_memunmap is wrong.
> > >
> > >Add the missing annotation.
> > >
> > >Fixes: e658c82be556 ("efi/tpm: Only set 'efi_tpm_final_log_size' after successful event log parsing")
> > >Signed-off-by: Arnd Bergmann <arnd@...db.de>
> >
> > Minor thing, but should the Fixes be c46f3405692d ("tpm: Reserve the TPM final events table")? Or what am I missing
> > about e658c82be556 that causes this? Just trying to understand what I did. :)
>
> You are right, I misread the git history. Can you fix it up when applying the
> patch, or should I resend it?
>
I can fix it up, no worries.
Powered by blists - more mailing lists