Re: [PATCH v4 10/29] x86/die: Don't try to recover from an OOPS on a non-default stack

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
Subject: Re: [PATCH v4 10/29] x86/die: Don't try to recover from an OOPS on a non-default stack
From: Borislav Petkov <bp@xxxxxxxxx>
Date: Sun, 3 Jul 2016 20:42:13 +0200
Cc: Josh Poimboeuf <jpoimboe@xxxxxxxxxx>, Andy Lutomirski <luto@xxxxxxxxxx>, X86 ML <x86@xxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, linux-arch <linux-arch@xxxxxxxxxxxxxxx>, Nadav Amit <nadav.amit@xxxxxxxxx>, Kees Cook <keescook@xxxxxxxxxxxx>, Brian Gerst <brgerst@xxxxxxxxx>, "kernel-hardening@xxxxxxxxxxxxxxxxxx" <kernel-hardening@xxxxxxxxxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, Jann Horn <jann@xxxxxxxxx>, Heiko Carstens <heiko.carstens@xxxxxxxxxx>
In-reply-to: <CALCETrVowqk90fmsg9eJG7Fvk0EMVFS0azCbJ89dioRtuXZOKQ@mail.gmail.com>
References: <cover.1466974736.git.luto@kernel.org> <37ac7589ff0ea147e8a21cda5eb84d3af1f6cd60.1466974736.git.luto@kernel.org> <20160702172441.GA22748@pd.tnic> <20160702183451.e2nlfkfxlsuicbqd@treble> <CALCETrVowqk90fmsg9eJG7Fvk0EMVFS0azCbJ89dioRtuXZOKQ@mail.gmail.com>
User-agent: Mutt/1.5.24 (2015-08-30)

On Sun, Jul 03, 2016 at 07:25:05AM -0700, Andy Lutomirski wrote:
> Given that the very next patch deletes this code, I vote for leaving
> it alone.  Or I could fold the patches together.

Ah, true. Yes, please fold them together.

-- 
Regards/Gruss,
Boris.

ECO tip #101: Trim your mails when you reply.
--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

References:
- [PATCH v4 00/29] virtually mapped stacks and thread_info cleanup
  - From: Andy Lutomirski
- [PATCH v4 10/29] x86/die: Don't try to recover from an OOPS on a non-default stack
  - From: Andy Lutomirski
- Re: [PATCH v4 10/29] x86/die: Don't try to recover from an OOPS on a non-default stack
  - From: Borislav Petkov
- Re: [PATCH v4 10/29] x86/die: Don't try to recover from an OOPS on a non-default stack
  - From: Josh Poimboeuf
- Re: [PATCH v4 10/29] x86/die: Don't try to recover from an OOPS on a non-default stack
  - From: Andy Lutomirski

Prev by Date: Re: [PATCH v4 10/29] x86/die: Don't try to recover from an OOPS on a non-default stack
Next by Date: Re: [PATCH v2 1/2] arm64: implement FTRACE_WITH_REGS
Previous by thread: Re: [PATCH v4 10/29] x86/die: Don't try to recover from an OOPS on a non-default stack
Next by thread: [PATCH v4 20/29] x86/smp: Remove stack_smp_processor_id()
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel] [Kernel Newbies] [x86 Platform Driver] [Netdev] [Linux Wireless] [Netfilter] [Bugtraq] [Linux Filesystems] [Yosemite Discussion] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Device Mapper]