linux-kernel - Re: [PATCH 0/6] loglevel=pci:8,acpi:8,apic=8 support v6

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: <20080918155041.GB3097@redhat.com>
Date:	Thu, 18 Sep 2008 11:50:41 -0400
From:	Jason Baron <jbaron@...hat.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Yinghai Lu <yhlu.kernel@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/6] loglevel=pci:8,acpi:8,apic=8 support v6

On Thu, Sep 18, 2008 at 08:36:43AM -0700, H. Peter Anvin wrote:
> Ingo Molnar wrote:
>>
>> which is what we really want. If a bootup fails, the user has to repeat 
>> the bootup at least once with a verbosity level increased and with  
>> (hopefully) some sort of log capture facility attached.
>>
>> So the point would be, if the user specified loglevel=all, we would get 
>> really comprehensive, one-stop-shop output.
>>
>
> That is true if the bootup fails, but it's fairly common that we get the  
> machine up (at least to the point when we can dmesg), but the user wants  
> to report a problem.  For that case, it's very nice if the dmesg log  
> contains as much information as possible.
>
> So I don't think it's clear that pre-filtering is what we want, at all.
>
> 	-hpa
>

hi,

if we take this argument to its extreme, then we end up spending all of
our time verifying that the kernel is working correctly and no time
actually doing work. I think 'printk_ratelimit' captures this. Thus, the line 
has to be drawn somewhere. If you want the messages in 'dmesg' use,
printk(KERN_DEBUG), and 'grep'. For the rest, I propose pre-filtering, which is
what 'dynamic debug' uses.

thanks,

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