linux-kernel - Re: [PATCH] - add "fixpae" bootparam to fix/workaround #930447

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]

Message-ID: <20131129124941.GA18950@bark>
Date:	Fri, 29 Nov 2013 12:49:41 +0000
From:	Andy Whitcroft <apw@...onical.com>
To:	Roland <devzero@....de>
Cc:	"H. Peter Anvin" <hpa@...or.com>, kernel-team@...ts.ubuntu.com,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] - add "fixpae" bootparam to fix/workaround #930447

On Wed, Nov 27, 2013 at 09:41:03PM +0100, Roland wrote:
> This patch is meant primarly for ubuntu, as they only ship PAE
> enabled kernels and don`t ship non-PAE kernels anymore.  So this
> resolves an ubuntu specific problem (as the installer disc also has
> PAE enabled kernel).
> 
> I know it`s not perfect, but poking cpu bits in arrays is above my
> skills and i have already spent really much time with this trying to
> resolve a problem for the end-user intruduced by nothing but the
> decision to discontinue Non-PAE kernels.

I think the complaints are more about how it works that the intent.
Kernel engineers are by their very nature very risk averse, so it would
indeed be good to set the bit correctly in the cpu capability flags, and
to do that based on the machine type.

I might just have a machine which exhibits this behaviour, I will try
and look it out and see if we can morph this into something appropriate.

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