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]
Message-ID: <20180213210438.GA6569@amd>
Date:   Tue, 13 Feb 2018 22:04:38 +0100
From:   Pavel Machek <pavel@....cz>
To:     Ondrej Zary <linux@...nbow-software.org>
Cc:     whiteheadm@....org, David Laight <David.Laight@...lab.com>,
        Arnd Bergmann <arnd@...db.de>,
        Alan Cox <gnomes@...rguk.ukuu.org.uk>,
        David Woodhouse <dwmw2@...radead.org>,
        Guenter Roeck <linux@...ck-us.net>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Hugh Dickins <hughd@...gle.com>,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        Jiri Kosina <jikos@...nel.org>, Borislav Petkov <bp@...en8.de>,
        Kees Cook <keescook@...omium.org>,
        Jamie Iles <jamie@...ieiles.com>,
        Eduardo Valentin <eduval@...zon.com>,
        Laura Abbott <labbott@...hat.com>,
        Rik van Riel <riel@...riel.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [BUG] x86 : i486 reporting to be vulnerable to
 Meltdown/Spectre_V1/Spectre_V2

Hi!

> > You might think this absolutely crazy, but I would be willing to test
> > such systems if I can get my hands on the needed hardware that I lack.
> > I am already doing sanity testing on Intel
> > i486/i586/i586-MMX/i686-PentiumPro systems, I just don't have the
> > clone cpus (Cyrix, etc).
> >
> > While few people are using the 32bit kernel, I don't think we want to
> > kill it completely just yet.
> 
> I have a working Cyrix MII (was actively using it last year, now upgraded to a 
> P3-based Celeron). Some AMD CPUs too - K6(maybe -2 or -3?), not sure about K5 
> and also a Rise mP6. But never got a WinChip.

I'm using Core Duo daily (backup machine, web browsing), and use
Pentium M as an ssh client say once in month.

> So the question is: what to test?

Self-compiling kernel is traditional stability test.

I do have two Geodes I believe, but the hardware is quite nasty to
use. (One has some kind of forth-based BIOS -- forgot the name).

> BTW. Kernel was not able to identify mP6 CPU 6 years ago, patches were 
> ignored.

You may want to re-send :-).
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ