linux-kernel - Re: [patch 0/8] debug printk infrastructure

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 23 May 2008 10:21:01 +1000
From:	Nick Andrew <nick@...k-andrew.net>
To:	Jason Baron <jbaron@...hat.com>
Cc:	akpm@...ux-foundation.org, joe@...ches.com, greg@...ah.com,
	randy.dunlap@...cle.com, linux-kernel@...r.kernel.org
Subject: Re: [patch 0/8] debug printk infrastructure

On Thu, May 22, 2008 at 05:13:31PM -0400, Jason Baron wrote:
> The debugfs file, then lists all the modules that can be 'enabled' for dynamic
> printk calls. Currently, the file has a 4 column format (excerpt from my system:

Nice work Jason.

If you write "enable all" to the debugfs file and then insmod a new
module, will debugging be enabled on the new module?

Nick.
-- 
PGP Key ID = 0x418487E7                      http://www.nick-andrew.net/
PGP Key fingerprint = B3ED 6894 8E49 1770 C24A  67E3 6266 6EB9 4184 87E7
--
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/