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] [day] [month] [year] [list]
Date:	Tue, 2 Sep 2014 08:57:53 +0200
From:	Anders Darander <anders@...rgestorm.se>
To:	Matt Fleming <matt@...sole-pimps.org>
CC:	Yinghai Lu <yinghai@...nel.org>,
	Matt Fleming <matt.fleming@...el.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Mantas Mikulėnas <grawity@...il.com>,
	"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Harald Hoyer <harald@...hat.com>
Subject: Re: [PATCH] x86: only load initrd above 4g on second try

* Matt Fleming <matt@...sole-pimps.org> [140830 13:24]:
> On Wed, 27 Aug, at 10:13:22AM, Yinghai Lu wrote:
> > How about adding more info print out like:
> >   "Try to load initrd file to higher address..."

> Yeah, that could work, at least we've had some debugging information to
> go on if people start reporting hangs, though I'd suggest using "Trying"
> or "Attempting".

That should be fine. That would at least give the user something easy to
search for (both web and source), and thus make it possible to at least
get an idea of why the boot is hanging for the few people that's going
to hit this.

For most systems, the default to load the initrd/initramfs below 4G (and
only load it above on the second attempt) will handle our buggy EFI's...

To me this sounds like something that should work.

Cheers,
Anders

-- 
Option Paralysis:
	The tendency, when given unlimited choices, to make none.
		-- Douglas Coupland, "Generation X: Tales for an Accelerated
		   Culture"
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ