| 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: <20081227185727.GB10442@uranus.ravnborg.org> Date: Sat, 27 Dec 2008 19:57:27 +0100 From: Sam Ravnborg <sam@...nborg.org> To: Ingo Molnar <mingo@...e.hu> Cc: Mike Frysinger <vapier@...too.org>, tglx@...utronix.de, mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH] x86 byteorder.h: use __asm__/__inline__ for userspace On Sat, Dec 27, 2008 at 09:47:08AM +0100, Ingo Molnar wrote: > > * Sam Ravnborg <sam@...nborg.org> wrote: > > > On Sat, Dec 27, 2008 at 01:50:04AM -0500, Mike Frysinger wrote: > > > Use __asm__/__inline__ rather than asm/inline for all the functions > > > exported to userspace. > > > > I will imagine that we will see cleanup patches converting > > these back to inline/asm. > > How about doing this conversion as part of the headers_install.pl > > script so we know it is always correct? > > > > Then we can keep the familiar inline/asm in the kernel headers > > and always use the correct __asm__, __inline__ version for our > > exported headers. > > or name it __asm__exported__ to make sure it isnt cleaned up away. I wnet with the scripted conversion for now. If that does not fly we can come back to this proposal. What I like most with the auto conversion is that we avoid adding yet another special rule about how to do stuff in exported headers. Sam -- 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