| 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: <AANLkTinLoDN_6zG56J7V154jrRc-K+BzAHFO3qS_r8J0@mail.gmail.com> Date: Tue, 25 Jan 2011 12:01:35 -0800 From: Mike Waychison <mikew@...gle.com> To: Greg KH <greg@...ah.com> Cc: torvalds@...ux-foundation.org, San Mehat <san@...gle.com>, Aaron Durbin <adurbin@...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 Mon, Jan 24, 2011 at 6:06 PM, Greg KH <greg@...ah.com> wrote: > On Mon, Jan 24, 2011 at 04:24:39PM -0800, Mike Waychison wrote: >> From: Aaron Durbin <adurbin@...gle.com> >> >> Later firmware patches in this series would like to be able to be >> notified whenever an oops occurs on the system, so that it can be >> recorded in the boot log. >> >> This patch introduces a notifier_block called "oops_notifier_list" >> so that drivers can register to get called whenever an Oops is >> triggered. > > But we already have a panic notifier list. Why create a new one? > What's wrong with the existing one that doesn't work properly for you? AFAICT, the panic notifier list doesn't get called on oops. Should we reuse it and actually add meaning to the 'reason' argument? It does become a misnomer if we do that :\ -- 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