[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220525125627.acf27b28bb67417a6683a1d9@linux-foundation.org>
Date: Wed, 25 May 2022 12:56:27 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Baoquan He <bhe@...hat.com>,
"Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>,
Michael Ellerman <mpe@...erman.id.au>,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
kexec@...ts.infradead.org
Subject: Re: [PATCH] kexec_file: Drop weak attribute from
arch_kexec_apply_relocations[_add]
On Fri, 20 May 2022 14:25:05 -0500 "Eric W. Biederman" <ebiederm@...ssion.com> wrote:
> > I am not strongly against taking off __weak, just wondering if there's
> > chance to fix it in recordmcount, and the cost comparing with kernel fix;
> > except of this issue, any other weakness of __weak. Noticed Andrew has
> > picked this patch, as a witness of this moment, raise a tiny concern.
>
> I just don't see what else we can realistically do.
I think converting all of the kexec __weaks to use the ifdef approach
makes sense, if only because kexec is now using two different styles.
But for now, I'll send Naveen's v2 patch in to Linus to get us out of
trouble.
I'm thinking that we should add cc:stable to that patch as well, to
reduce the amount of problems which people experience when using newer
binutils on older kernels?
Powered by blists - more mailing lists