lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 23 Jul 2015 14:35:08 -0700 From: Linus Torvalds <torvalds@...ux-foundation.org> To: Peter Zijlstra <peterz@...radead.org> Cc: Andy Lutomirski <luto@...capital.net>, X86 ML <x86@...nel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Willy Tarreau <w@....eu>, Borislav Petkov <bp@...en8.de>, Thomas Gleixner <tglx@...utronix.de>, Steven Rostedt <rostedt@...dmis.org>, Brian Gerst <brgerst@...il.com> Subject: Re: Dealing with the NMI mess On Thu, Jul 23, 2015 at 2:20 PM, Peter Zijlstra <peterz@...radead.org> wrote: > > So the NMI could trigger userspace debug register faults, and simply > disabling them would make the whole debug register thing entirely > unreliable. We could easily set something to re-enable them for when we actually return to user space. I'd be ok with just setting the _TIF_USER_WORK_MASK. But even that should not be a requirement for the basic stability and core integrity of the kernel. Not like the current horrid mess with NMI nesting and ESP fixing etc. And realistically, nobody will ever even notice. So the whole "ok, we can use _TIF_USER_WORK_MASK to re-enable dr7" is a tiny tiny detail that is more like cleaning up things, not a core issue. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists