linux-kernel - Re: [userns:userns-always-map-user-v45 80/99] fs/namespace.c:2290:1: error: unknown type name 'atomic64

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:	Tue, 14 Aug 2012 02:13:43 +0800
From:	Fengguang Wu <fengguang.wu@...el.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	kernel-janitors@...r.kernel.org, Greg Ungerer <gerg@...inux.org>,
	linux-m68k@...ts.linux-m68k.org, linux-kernel@...r.kernel.org
Subject: Re: [userns:userns-always-map-user-v45 80/99] fs/namespace.c:2290:1:
 error: unknown type name 'atomic64_t'

On Tue, Aug 14, 2012 at 01:55:16AM +0800, Fengguang Wu wrote:
> > >I'd suggest to fix it in m68k and make atomic64_t generally available.
> > 
> > Fengguang in your testing on any architechtures is atomic64_t missing on anything except some m68k subarchtechtures?
> 
> Eric, it only complaints for m68k, among the architechtures the build
> tests covered (alpha arm avr32 blackfin cris frv h8300 i386 ia64 m32r
> m68k mips mn10300 openrisc parisc powerpc s390 sh sparc sparc64 tile
> um x86_64 xtensa).

Sorry, I must missed something (in my system, build errors are only
recorded on first sight)..

wfg /c/linux% for arch in arch/*/; do grep -ir -q atomic64 $arch || echo $arch; done
arch/c6x/
arch/h8300/
arch/mn10300/
arch/score/
arch/unicore32/

So the above archs are likely still missing atomic64_t support.
However it should be trivial to add support to them, by adding
"select GENERIC_ATOMIC64" lines to them.

Thanks,
Fengguang
--
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/