| 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: <AANLkTikyMswC7eNaambOAmCVQ3uxcZSiikigkTOxYciE@mail.gmail.com> Date: Wed, 26 Jan 2011 13:50:06 -0800 From: Mike Waychison <mikew@...gle.com> To: Greg KH <greg@...ah.com> Cc: Aaron Durbin <adurbin@...gle.com>, Jeff Garzik <jeff@...zik.org>, torvalds@...ux-foundation.org, San Mehat <san@...gle.com>, Duncan Laurie <dlaurie@...gle.com>, linux-kernel@...r.kernel.org, Tim Hockin <thockin@...gle.com> Subject: Re: [PATCH v1 1/6] Add oops notification chain. On Tue, Jan 25, 2011 at 6:48 PM, Greg KH <greg@...ah.com> wrote: > On Tue, Jan 25, 2011 at 02:21:03PM -0800, Aaron Durbin wrote: >> As Mike talked about it might be more desirable to actually pass a >> reason field that indicates the appropriate kernel event. However, the >> naming of some of the variables becomes less clear. Maybe name it >> panic_oops_notifier_list? That way there would only be a single >> notifier chain. > > Yes, I think that's the better thing to do here instead of adding more > notifier chains. It would just start to get even messier than it > currently is :) Hmm. I'm going to try and just re-use the notify_die() bits here instead which seems to do what I want. The overloading of "die" is a bit of a mess, which is probably why I missed it the first time around. -- 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