[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrXXTijS0pbd2n9Rh_1AMsaerbGxC06mDmXoYm8rCDKpvg@mail.gmail.com>
Date: Sun, 3 Jul 2016 07:36:30 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Borislav Petkov <bp@...en8.de>
Cc: Dave Hansen <dave.hansen@...ux.intel.com>,
Michal Hocko <mhocko@...e.com>, X86 ML <x86@...nel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
stable <stable@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Dave Hansen <dave@...1.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 1/6] x86: fix duplicated X86_BUG(9) macro
On Jul 1, 2016 9:47 AM, "Borislav Petkov" <bp@...en8.de> wrote:
>
> On Fri, Jul 01, 2016 at 09:30:37AM -0700, Andy Lutomirski wrote:
> > I put the ifdef there to prevent anyone from accidentally using it in
> > a 64-bit code path, not to save a bit. We could put in the middle of
> > the list to make the mistake much less likely to be repeated, I
> > suppose.
>
> Well, if someone does, someone will notice pretty soon, no?
Dunno. ESPFIX was broken under KVM for years and no one notices.
>
> I just don't see the reason to worry but maybe I'm missing it.
>
> And we can call it X86_BUG_ESPFIX_X86_32 or so too...
We could do that, too, I guess. But the current solution is only two
extra lines of code. We could reorder the things so that it's in the
middle instead of at the end, I suppose.
--Andy
Powered by blists - more mailing lists