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>] [day] [month] [year] [list]
Date:	Mon, 26 Apr 2010 11:31:19 +0200
From:	Sven Eckelmann <sven.eckelmann@....de>
To:	linux-kernel@...r.kernel.org
Subject: Range of 24/32 bit for atomic_t since 2.6.3

Hi,

currently arch/mn10300/include/asm/atomic.h and include/asm-generic/atomic.h 
warns right before atomic_read/atomic_set/atomic_add_return/ atomic_sub_return 
that atomic_t only guarantees a useful range of 24 bits. 
Documentation/atomic_ops.txt informs about the historical reason why this was 
true for 32-bit Sparc - something that was changes in linux 2.6.3 using a hash 
array with spinlocks [1].

Is it save to assume that atomic_t provides us the full range of 32 bit after 
2.6.3 and can those statements in both atomic.h be removed?

Kind regards,
	Sven Eckelmann

[1] http://lwn.net/Articles/71732/

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ