linux-kernel - Re: [PATCH 2/2] asm-generic: Don't warn that atomic

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]

Message-Id: <20100428.094652.22534047.davem@davemloft.net>
Date:	Wed, 28 Apr 2010 09:46:52 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	peter.fritzsche@....de
Cc:	arnd@...db.de, mingo@...e.hu, akpm@...ux-foundation.org,
	heiko.carstens@...ibm.com, mathieu.desnoyers@...ymtl.ca,
	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
	wesolows@...bazco.org
Subject: Re: [PATCH 2/2] asm-generic: Don't warn that atomic_t is only 24
 bit

From: Peter Fritzsche <peter.fritzsche@....de>
Date: Wed, 28 Apr 2010 13:10:36 +0200

> 32-bit Sparc used to only allow usage of 24-bit of it's atomic_t type.
> This was corrected with linux 2.6.3 when Keith M Wesolowski changed the
> implementation to use the parisc approach of having an array of
> spinlocks to protect the atomic_t.
> 
> These warnings were also removed from the sparc implementation when the
> new implementation was merged in BKrev:402e4949VThdc6D3iaosSFUgabMfvw,
> but the warning still remained in some other places without any
> 24-bit-only atomic_t implementation inside the kernel.
> 
> We should remove these warnings to allow users to rely on the full
> 32-bit range of atomic_t.
> 
> Signed-off-by: Peter Fritzsche <peter.fritzsche@....de>

Acked-by: David S. Miller <davem@...emloft.net>
--
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/