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: Sun, 6 Jan 2008 13:38:17 -0800 From: Arjan van de Ven <arjan@...radead.org> To: Olof Johansson <olof@...om.net> Cc: linux-kernel@...r.kernel.org, akpm@...ux-foundation.org, heiko.carstens@...ibm.com, mingo@...e.hu, mpm@...enic.com Subject: Re: [PATCH] Add bug/warn marker to generic report_bug() On Sun, 6 Jan 2008 14:22:23 -0600 Olof Johansson <olof@...om.net> wrote: > Powerpc uses the generic report_bug() from lib/bug.c to report > warnings, and I'm guessing other arches do as well. > > Add the module list as well as the end-of-trace marker to the output. > This required making print_oops_end_marker() nonstatic. > > this is the wrong approach... powerpc and such should just use oops_enter() / oops_exit() to signal the start/end of such a trace, that gives them all the other behavior of oopsing as well (such as the "slow oops scrolling down" etc) -- 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