linux-kernel - Re: [RFC PATCH 0/2] ARM: Remove any correlation between IPC and BogoMips value

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, 8 May 2013 10:06:44 +0100
From:	Will Deacon <will.deacon@....com>
To:	Christopher Covington <cov@...eaurora.org>
Cc:	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Marc Zyngier <Marc.Zyngier@....com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 0/2] ARM: Remove any correlation between IPC and
 BogoMips value

Hello Christopher,

On Tue, May 07, 2013 at 04:48:26PM +0100, Christopher Covington wrote:
> On 05/07/2013 05:08 AM, Will Deacon wrote:
> > That seems like a lot of effort in order to preserve something that isn't
> > even meaningful. We might be better just zeroing the value, but then we'll
> > inevitably get bug reports of it being `wrong'.
> 
> If I were in to filing bug reports about bogomips values, I would be just as
> likely to do it for 1, 10000, 99999, and get_random_bytes(...) as for 0.

That's a fair point, and one of the reasons I posted this as an RFC. I'd
basically like an `obviously bogus' value so that people don't think `hey,
my CPU sure it slow' and instead think `looks like this really is a bogus
value after all'.

However, you're probably right that there isn't a number which can convey
that information properly, so how about we just put a string in there along
the lines of "not reported" and leave it at that?

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