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]
Date:	Wed, 27 Nov 2013 21:41:03 +0100
From:	"Roland" <devzero@....de>
To:	"H. Peter Anvin" <hpa@...or.com>, <kernel-team@...ts.ubuntu.com>
Cc:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] - add "fixpae" bootparam to fix/workaround #930447

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.

If grub2 can do nasty or ugly things like skipping standard x86 bootcode 
(which also skips validate_cpu() - while nobody seems to have a problem with 
that) , then i don`t understand what´s the real problem to add a very simple 
and unintrusive quirk to a vendor specific kernel.

Let time go by and the quirk will be obsolete one day anyway as no hardware 
lives forever.

But for now there exist distros like lubuntu meant for older hardware, and 
if installing that on a Pentium M 1,7 Ghz fails because of that nasty PAE 
issue nobody is willing to fix elegantly, then i think it deserves only one 
term:

planned obsolescence

I`s bad enough, that industry does produce products with limited lifetime. 
Products that break and that even can`t be repaired.

So please, kernel people, don`t think that way. Care for the users.

Many thinkpad users will be thankful if they can install their favourite 
distro by just adding a bootparam instead of reading through tons of pages 
how to add even weirder workarounds like bind-mounting a modified copy of 
itself on top of /proc/cpuinfo.

regards
Roland

ps:
https://help.ubuntu.com/community/Lubuntu-fake-PAE

--------------------------------------------------
From: "H. Peter Anvin" <hpa@...or.com>
Sent: Wednesday, November 27, 2013 12:33 AM
To: "Roland Kletzing" <devzero@....de>; <kernel-team@...ts.ubuntu.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] - add "fixpae" bootparam to fix/workaround #930447

> On 11/26/2013 03:09 PM, Roland Kletzing wrote:
>> Hello kernel-team,
>>
>> regarding https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/930447 
>> , i have developed a simple patch to (hopefully) provide an easy and 
>> elegant workaround/fix for the issue. I assume some hundred users (if not 
>> some thousand, as entries in bugreports are only the tip of an iceberg) 
>> are affected by this issue.
>>
>> Please take a review and feel free to merge.
>>
>> As defaulting to PAE kernels is specific for some distros only, i think 
>> this is no patch for mainline (yet).
>>
>> I did not often do patches, nor am i a good programmer - so sorry if the 
>> patch or the submission style is not perfect.
>>
>> regards
>> Roland
>
> No, this is not an acceptable patch per se.
>
> The right way to do this is to have the option, if it is found, simply
> set the bit in the CPU array.  However, it is important to verify that
> we are on the affected type of CPU, specifically the affected Pentium Ms.
>
> x86 patches should be sent to <x86@...nel.org> or equivalently myself,
> <mingo@...nel.org> and <tglx@...utronix.de> and Cc:
> <linux-kernel@...r.kernel.org>.  I also encourage you to read the file
> Documentation/SubmittingPatches before trying again.
>
> -hpa
> 
--
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