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]
Date:	Mon, 2 Aug 2010 16:13:59 +0200
From:	Thomas Renninger <trenn@...e.de>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	Jason Baron <jbaron@...hat.com>, Greg KH <gregkh@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, bjorn.helgaas@...com
Subject: Re: Boot-time dynamic debugging?

On Monday 02 August 2010 15:53:24 Pekka Enberg wrote:
> > On Sun, Aug 01, 2010 at 03:10:40PM +0300, Pekka Enberg wrote:
> >> Commit 346e15beb5343c2eb8216d820f2ed8f150822b08 ("driver core: basic
> >> infrastructure for per-module dynamic debug messages") removed
> >> "dynamic_printk" kernel parameter from the dynamic debugging subsystem
> >> (and forgot to update Documentation/kernel-parameters.txt). How can I
> >> use the new subsystem for enabling boot-time dev_dbg() calls for
> >> non-modular kernels?
> 
> On Mon, Aug 2, 2010 at 4:47 PM, Jason Baron <jbaron@...hat.com> wrote:
> > Right now, you can not enable them dynamically from the boot command
> > line (only via the debugfs file). However, Thomas Renninger, has posted
> > a series to add back the boot-time functionality, see:
> >
> > Subject:    [patch 0/3] Dynamic Debug providing early boot debug messages via
> > boot parameter
> > http://marc.info/?l=linux-kernel&m=127970474426120&w=2
> >
> > So I intend to queue those up for 2.6.36, and also update the
> > documentation.
> 
> Oh, great!
> 
> Acked-by: Pekka Enberg <penberg@...helsinki.fi>
Thanks.
> 
> Btw, can you easily enable all dev_dbg() calls with the boot parameter?
I expect yes, but never explicitly tried it, dev_dbg should result in
printk(KERN_DEBUG ...) after some macro/inline func processing.

Be aware that I sent another neat ddebug functionality:
Subject on LKML: [PATCH] Dynamic Debug: Introduce global fake module param module.ddebug

If, take the second post (same mail thread) which is the same patch
with some documentation added.
It's based on top of the patchseries mentioned above.
Would be great if someone could pick it up as well.
I was not sure about the fact that drivers must not use ddebug as parameter
anymore with this patch and how to document that, quick review and/or
comments appreciated.

Thanks,

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