On Mon, Mar 9, 2015 at 7:16 PM, Linus Torvalds <[email protected]> wrote: > On Mon, Mar 9, 2015 at 11:04 AM, Andy Lutomirski <[email protected]> wrote: >> >> One option would be to change the NMI entry code to move itself down 8 >> bytes if this happens (came from kernel mode or sp == sp0 - 12, >> perhaps). > > Hmm. That whole code currently depends on the stack setup being just a > single instruction (the move to esp). And that simplifies things, I'd > like to keep it that way. > > I'd *much* rather just keep the 8-byte padding. What was so > problematic with that? It worked. It's been around forever. Removing > it is the bug.
Unfortunately, looks like keeping the gap is the safest thing to do. Hopes that tss.sp0 was true top of the stack, sans "a few little problems", died so quickly :/ (and we didn't even touch vm86 yet). We probably better off to give that 8 a name. Now it's just another magic constant in the entry.S maze. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
