linux-kernel - Re: don't taint UP K7's running SMP kernels. II

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <p737j1pz5dz.fsf@verdi.suse.de>
Date:	04 Aug 2006 02:55:20 +0200
From:	Andi Kleen <ak@...e.de>
To:	Dave Jones <davej@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: don't taint UP K7's running SMP kernels. II

Dave Jones <davej@...hat.com> writes:

> We have a test that looks for invalid pairings of certain athlon/durons
> that weren't designed for SMP, and taint accordingly (with 'S') if we find
> such a configuration.  However, this test shouldn't fire if there's only
> a single CPU present. It's perfectly valid for an SMP kernel to boot on UP
> hardware for example.

Actually the test should be for num_possible_cpus() I fixed this.

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