| 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
| ||
|
Message-ID: <CALCETrV-bXgMPOkjvEuBwyCAU-cS5aw3i54wGQ7w9cwqfLt1tg@mail.gmail.com> Date: Thu, 12 Nov 2015 12:04:36 -0800 From: Andy Lutomirski <luto@...capital.net> To: "Luck, Tony" <tony.luck@...el.com> Cc: Andy Lutomirski <luto@...nel.org>, Borislav Petkov <bp@...en8.de>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, linux-edac <linux-edac@...r.kernel.org>, X86 ML <x86@...nel.org>, DanWilliamsdan.j.williams@...el.com Subject: Re: [PATCH 1/3] x86, ras: Add new infrastructure for machine check fixup tables On Thu, Nov 12, 2015 at 11:44 AM, Luck, Tony <tony.luck@...el.com> wrote: > On Wed, Nov 11, 2015 at 08:14:56PM -0800, Andy Lutomirski wrote: >> On 11/06/2015 12:57 PM, Tony Luck wrote: >> >Copy the existing page fault fixup mechanisms to create a new table >> >to be used when fixing machine checks. Note: >> >1) At this time we only provide a macro to annotate assembly code >> >2) We assume all fixups will in code builtin to the kernel. >> >> Shouldn't the first step be to fixup failures during user memory access? > > We already have code to recover from machine checks encountered > while the processor is executing ring3 code. I meant failures during copy_from_user, copy_to_user, etc. --Andy -- 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