linux-kernel - Re: [PATCH V2] x86: Allow built-in command line to work in early kernel init

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAPeXnHtnspcpa2zZLzwVxUtctgGDRgX=gKp933HCSPgjj7wNFg@mail.gmail.com>
Date:	Wed, 3 Jun 2015 09:08:11 -0700
From:	Matthew Garrett <mjg59@...eos.com>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	hpa@...or.com, yinghai@...nel.org, x86@...nel.org,
	mingo@...hat.com, tglx@...utronix.de,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V2] x86: Allow built-in command line to work in early
 kernel init

On Wed, Jun 3, 2015 at 2:24 AM, Ingo Molnar <mingo@...nel.org> wrote:
> It's all pretty non-trivial, so it has to be finegrained, perfectly bisectable,
> etc.

Yeah. I'm not really going to be able to justify the time for that -
this is code that dates back a long way, there's undoubtedly
subtleties throughout and the potential for breaking things is pretty
significant (plus I'm certainly not sure that I understand it all - I
grew up on actual CPUs, not these awful segmented things). I'll figure
out something we can use locally and leave this for now. Thanks for
the feedback!
--
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/