linux-kernel - Re: [tip:sched/urgent] sched: sched_getaffinity(): Allow less than NR

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 15 Mar 2010 09:17:06 -0700
From:	Ulrich Drepper <drepper@...hat.com>
To:	Jack Steiner <steiner@....com>
CC:	mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, travis@....com,
	peterz@...radead.org, rja@....com, sharyath@...ibm.com,
	akpm@...ux-foundation.org, tglx@...utronix.de,
	kosaki.motohiro@...fujitsu.com, mingo@...e.hu,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:sched/urgent] sched: sched_getaffinity(): Allow less than
 NR_CPUS length

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/15/2010 09:04 AM, Jack Steiner wrote:
> I'm running on a distro kernel that has NR_CPUS=4096.  Glibc has also has a
> definition of __CPU_SETSIZE (I assume this change was made by the distro but
> am not certain):

This isn't upstream and it cannot.  Whoever make this change doesn't
know what binary compatibility means.  The size has always been 1024 bits.

- -- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkueXYIACgkQ2ijCOnn/RHQJPQCbBvh+Mi7ZrHaQcVxEkglIj+Pz
j7UAoJaBCpD2a5KbAR1VGkM7orp+GBhY
=T78A
-----END PGP SIGNATURE-----
--
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/