linux-kernel - Re: [PATCH 6/7] remove all remaining

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:	Mon, 28 Aug 2006 10:53:11 +0200
From:	Andi Kleen <ak@...e.de>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	David Miller <davem@...emloft.net>, arnd@...db.de,
	linux-arch@...r.kernel.org, jdike@...toit.com, B.Steinbrink@....de,
	arjan@...radead.org, chase.venters@...entec.com, akpm@...l.org,
	rmk+lkml@....linux.org.uk, rusty@...tcorp.com.au,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 6/7] remove all remaining _syscallX macros



> /usr/include/linux is _not_ a place to dump "reference code" in lieu of
> documentation on using kernel interfaces.

At least for the system call interface it was always. It is not
my fault you're trying to suddenly redefine it to be something else.

> 
> Besides, the _syscallX implementations in the kernel were generally
> unsuitable for use 

I disagree. I used them and they worked great for me.

> in that way anyway -- I'd be much more inclined to 
> rely on the libc version. The kernel version would do strange things
> like break with PIC code by using an unavailable register (i386),
> misalign 64-bit syscall arguments on 32-bit machines (MIPS), etc. 

The glibc versions would do similar things. Just try to use a 6 argument
call on i386 for once.

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