linux-kernel - Re: [GIT PATCH] driver core patches for your 2.6-git tree

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: <20081017180133.GB2429@suse.de>
Date:	Fri, 17 Oct 2008 11:01:33 -0700
From:	Greg KH <gregkh@...e.de>
To:	Jason Baron <jbaron@...hat.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...e.hu,
	yhlu.kernel@...il.com, tglx@...utronix.de
Subject: Re: [GIT PATCH] driver core patches for your 2.6-git tree

On Fri, Oct 17, 2008 at 11:31:51AM -0400, Jason Baron wrote:
> 
> One concern, raised in the other thread was that subsystems might want
> to use their own defined tags, as opposed to KBUILD_MODNAME, which is
> used by default to group together debugging control. Layering this tag
> ability on top of this patchset is not hard, and I already have patches
> which begin to do that.

That sounds like a useful thing to have.

> Also, this patch allows passing one command line argument to enable
> all debugging which can later be turn on/off as desired. This patch
> already stands on its own in enabling all pr_debug and dev_dbg calls
> to be dynamically enabled.

I tried turning everything on once.  The output was almost unusable, you
pretty much always want to be able to pick and choose what you want
enabled otherwise you drown in irrelevant data :)

thanks,

greg k-h
--
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/