linux-kernel - Re: [PATCH 1/6] i386/x86_64: Allow disabling the putstr's from compressed boot wrapper

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: <200705251650.50471.jbarnes@virtuousgeek.org>
Date:	Fri, 25 May 2007 16:50:50 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Ben Collins <ben.collins@...ntu.com>,
	Andi Kleen <andi@...stfloor.org>,
	Ben Collins <bcollins@...ntu.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/6] i386/x86_64: Allow disabling the putstr's from compressed boot wrapper

On Friday, May 25, 2007 4:43:41 H. Peter Anvin wrote:
> Jesse Barnes wrote:
> > Right, but you're special that way.  And moreover, you would know how to
> > add such debug statements as needed.  But is this output something we
> > really need enabled unconditionally for everyone?
>
> *I* can do that, yes, but I usually don't have access to the platform in
> question.
>
> As such I really don't want to see this as a compilation option.  Make
> it a runtime option[*] so the user with the problematic machine.
>
> > I personally don't care that much, aside from the feeling that we have
> > way too many printks in general...
>
> [*] FWIW, my setup rewrite has a proper command-line parser in it, so we
> can use the command line from the start.

Yeah, that sounds much better.  Then it can just be under the usual 'debug' 
command line option.

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