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>] [day] [month] [year] [list]
Message-ID: <CAP8WD_bdE0Ee_YmnTJLvFo+Mf6_MfOPzezW4kq+zcKhuPe3urw@mail.gmail.com>
Date:   Thu, 13 Dec 2018 11:17:19 -0500
From:   tedheadster <tedheadster@...il.com>
To:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Can we drop upstream Linux x32 support?

I will also complain. I use the 32 bit x86 environment regularly for
testing. I have found several bugs and worked with upstream developers
to create fixes.

The developers never said anything like "this is a waste of time
because it was found on 32 bit". Instead, they were universally
supportive.

As an example, Thomas Gleixner said that the problem we found would
only show up on older hardware, and he affirmed that it was a bug that
certainly needed to be fixed ("NOHZ: Check for nohz active instead of
nohz enabled").

I actually think this is an _opportunity_ to engage aspiring kernel
programmers. Give them some guidance and have them actively test and
do simple maintenance of 32 bit x86. Yes, I am prepared to take the
lead on this if it is something you want to pursue.

- Matthew Whitehead

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ