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]

Date:	Thu, 18 Sep 2008 08:36:43 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Jason Baron <jbaron@...hat.com>,
	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

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

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