[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87bm9v28rh.fsf@xmission.com>
Date: Tue, 21 Aug 2018 14:40:02 +0200
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Nick Desaulniers <ndesaulniers@...gle.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Peter Anvin <hpa@...or.com>,
Simon Horman <horms@...ge.net.au>,
Andrew Morton <akpm@...ux-foundation.org>,
natechancellor@...il.com,
"the arch\/x86 maintainers" <x86@...nel.org>,
Philippe Ombredanne <pombredanne@...b.com>,
Kate Stewart <kstewart@...uxfoundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kexec Mailing List <kexec@...ts.infradead.org>
Subject: Re: [PATCH] x86/kexec: prefer _THIS_IP_ to current_text_addr
Linus Torvalds <torvalds@...ux-foundation.org> writes:
> On Mon, Aug 20, 2018 at 10:58 AM Nick Desaulniers
> <ndesaulniers@...gle.com> wrote:
>>
>> + akpm, Linus
>>
>> Bumping for review.
>
> Ugh. I am not personally a huge fan of this endless "fix up one at a time".
>
> Just do a patch that removes current_text_addr() entirely and be done
> with it, if that's what we want the end result to be.
>
> Don't bother with these small "let's remove the remaining ones one by
> one". Just get it over and done with.
One is generic code the other is assembly but the both appear to do the
same thing without unexpected complexity.
That said the patch earlier in this thread has clearly never been
compiled as it is using THIS_IP instead of _THIS_IP_ and there is not
a define of THIS_IP in the kernel.
Eric
Powered by blists - more mailing lists