linux-kernel - Re: [patch] use __asm__ and __volatile_

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] [day] [month] [year] [list]

Message-ID: <20070618181201.GB15922@infradead.org>
Date:	Mon, 18 Jun 2007 19:12:01 +0100
From:	Christoph Hellwig <hch@...radead.org>
To:	Robert Hancock <hancockr@...w.ca>
Cc:	David Woodhouse <dwmw2@...radead.org>,
	Arnd Bergmann <arnd@...db.de>,
	Arjan van de Ven <arjan@...radead.org>,
	Mike Frysinger <vapier@...too.org>, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org,
	rmk@....linux.org.uk
Subject: Re: [patch] use __asm__ and __volatile__ in i386/arm/s390 byteorder.h

On Mon, Jun 18, 2007 at 08:27:15AM -0600, Robert Hancock wrote:
> If we expect userspace apps to include them, then I would vote for no, 
> not for anything outside of #ifdef __KERNEL__ in exported headers. Keep 
> in mind also that C++ apps may need to include these as well and those 
> extensions don't always play well in C++ mode. (Last instance I ran into 
> was the ioctl argument checking macros _IOR, _IOW, etc. that create 
> non-compiling code if you use them in a C++ program.)

There's absolutely no reason to obfucate kernel headers for usage in
C++ source files.

-
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/