linux-kernel - Re: [PATCH] x86: Add portable getcpu call

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 Sep 2006 14:39:59 +0200
From:	Heiko Carstens <heiko.carstens@...ibm.com>
To:	Andi Kleen <ak@...e.de>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Martin Schwidefsky <schwidefsky@...ibm.com>
Subject: Re: [PATCH] x86: Add portable getcpu call

> > So this means that the contents of getcpu_cache will look completely
> > different if a process runs in 32bit mode or 64bit mode. Even if you're
> > saying "user programs should not..." this looks odd to me.
> > Is this really on purpose and do you really think that no user space
> > application will ever rely on the format of getcpu_cache?
> 
> The vsyscalls do, but if anything else does it deserves breaking.
> In the user headers it will also be just a array blob.

Ah, ok. The blob thing is the part I missed then.

> I was considering to xor it with a random value to bring the point across
> more strongly, but then didn't do it. Do you think I should? 

No, I don't think that will help much.
-
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/