| 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: Fri, 21 Feb 2014 15:22:34 -0800 From: Joe Perches <joe@...ches.com> To: LKML <linux-kernel@...r.kernel.org> Cc: Andrew Morton <akpm@...ux-foundation.org>, Kay Sievers <kay.sievers@...y.org>, Jason Wessel <jason.wessel@...driver.com> Subject: printk and kdb - dev_<level> not trapped/forwarded dev_<level> output does not use printk() but directly calls vprintk_emit(). kdb only traps direct printk() calls. So, kdb hasn't emitted any dev_<level> or netdev_<level> output since structured logging and vprintk_emit() was introduced a couple of years ago. It seems no one has cared. Maybe the kdb handling should be removed? -- 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