linux-kernel - Re: early_printk accessing __log

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: <20070724111215.8d91dc7c.akpm@linux-foundation.org>
Date:	Tue, 24 Jul 2007 11:12:15 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Robin Getz <rgetz@...ckfin.uclinux.org>
Cc:	"Mike Frysinger" <vapier.adi@...il.com>,
	linux-kernel@...r.kernel.org, "Greg Ungerer" <gerg@...pgear.com>,
	"Russell King" <rmk@....linux.org.uk>,
	"Paul Mundt" <lethal@...ux-sh.org>,
	"Tim Bird" <tim.bird@...sony.com>, bryan.wu@...log.com
Subject: Re: early_printk accessing __log_buf

On Tue, 24 Jul 2007 13:50:44 -0400
Robin Getz <rgetz@...ckfin.uclinux.org> wrote:

> > Lots of the kernel is pretty crappy.  One of our main tools for fixing
> > that is to ensure that new stuff is non-crappy.
> 
> No problem - I wasn't advocating putting something that you thought was crappy 
> into your tree (afterall that would be futile).

You wouldn't be the first ;)

> Other than making the 
> overhead high - is there a way to make it less crappy?
> 
> If the answer is no, and Mike's latest suggestion/patch is OK - that is what I 
> will live with - and tell people to spend more on their power supply.

Oh well, it sounds like we need the super-duper fast version.  Keep it as
simple as possible, please.

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