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, 13 Feb 2020 08:05:09 -0800 From: Andy Lutomirski <luto@...capital.net> To: Borislav Petkov <bp@...en8.de> Cc: "Luck, Tony" <tony.luck@...el.com>, X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [RFC PATCH 0/5] New way to track mce notifier chain actions > On Feb 12, 2020, at 10:09 PM, Borislav Petkov <bp@...en8.de> wrote: > > On Wed, Feb 12, 2020 at 09:52:39PM -0800, Andy Lutomirski wrote: >> I HATE notifier chains for exceptions, and I REALLY HATE NOTIFY_STOP. >> I don't suppose we could rig something up so that they are simply >> notifiers (for MCE and, eventually, for everything) and just outright >> prevent them from modifying the processing? > > As in: they all get executed unconditionally and there's no NOTIFY_STOP > and if they're not interested in the notification, they simply return > early? > > Hohumm, sounds nicer. > Exactly :) > -- > Regards/Gruss, > Boris. > > https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists