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]

Message-Id: <1156759232.5340.36.camel@pmac.infradead.org>
Date:	Mon, 28 Aug 2006 11:00:32 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Andi Kleen <ak@...e.de>
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

On Mon, 2006-08-28 at 10:53 +0200, Andi Kleen wrote:
> 
> > /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.

I'm trying to 'suddenly redefine' kernel headers as something that
_isn't_ just a library of random crap for people to abuse in userspace
as they see fit, then whine when something breaks even though it was
never really guaranteed to work when abused in that way anyway.

So far, you're just reminding me why that needed to be done.

> > Besides, the _syscallX implementations in the kernel were generally
> > unsuitable for use [as a reference implementation]
> 
> I disagree. I used them and they worked great for me.

Really? You used them as a reference implementation? Didn't you already
know how x86_64 syscalls work?

Or were you saying you just happened to use the x86_64 implementation of
_syscallX stuff in some userspace hacks, and it happened to work? In
which case go and line up behind the guy who said that about atomic.h on
i386 and only ever tested it on UP. The doctor will get to you later.

-- 
dwmw2

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