| 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
| ||
|
Message-Id: <1231346658.10383.2.camel@macbook.infradead.org> Date: Wed, 07 Jan 2009 16:44:18 +0000 From: David Woodhouse <dwmw2@...radead.org> To: Sam Ravnborg <sam@...nborg.org> Cc: "H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...e.hu>, Mike Frysinger <vapier@...too.org>, tglx@...utronix.de, mingo@...hat.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH] x86 byteorder.h: use __asm__/__inline__ for userspace On Sat, 2008-12-27 at 20:12 +0100, Sam Ravnborg wrote: > > Speaking of what we want to use in exported headers. > What is the recommendation with respect to uint32_t and friends? > To my best knowledge they are banned in exported headers as they > are not part of the kernel namespace and I see few users too. > But is this something we should check for? No, they're not banned. There are a few cases where they can't be used and we have to use the kernels "speshul" __u32 types, because certain headers get included by glibc and we can't "pollute" the namespace with the C standard types. But in _most_ cases, using the standard C types is just fine. -- David Woodhouse Open Source Technology Centre David.Woodhouse@...el.com Intel Corporation -- 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/
Powered by blists - more mailing lists