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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <009201c8cf58$58909080$09b1b180$@css.fujitsu.com>
Date:	Mon, 16 Jun 2008 11:26:12 +0900
From:	"Takashi Nishiie" <t-nishiie@...css.fujitsu.com>
To:	"'Jason Baron'" <jbaron@...hat.com>, <akpm@...ux-foundation.org>
Cc:	<linux-kernel@...r.kernel.org>, <joe@...ches.com>,
	<greg@...ah.com>, <nick@...k-andrew.net>, <randy.dunlap@...cle.com>
Subject: RE: [PATCH 0/8] dynamic debug

Hi.

Jason Baron wrote:
>Each kernel sub-system seems to have its own way of dealing with 
>debugging statements. Some of these methods include 'dprintk', 
>'pr_debug', 'dev_debug', 'DEBUGP'. There are also a myriad of 
>ways of enabling these statements. 

 I propose to replace 'Pr_debug', 'Dev_debug', and 'DEBUGP' with 
kernel markers. SystemTap is used for the output of the log.  

 I propose to make it to the function to output only specified 
kernel markers as a log and the function in a word like LTTng of
a simple version by using the framework and kernel markers of 
ftrace if the log is output by using debugfs. 

Thank you,

--
Takashi Nishiie



--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ