linux-kernel - Re: OT: calling kernel syscall manually

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1158169957.18619.199.camel@pmac.infradead.org>
Date:	Wed, 13 Sep 2006 18:52:37 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	guest01 <guest01@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: OT: calling kernel syscall manually

On Wed, 2006-09-13 at 18:52 +0200, guest01 wrote:
> So these macros are no longer available in the latest kernel versions?
> Ok, if that's true, I will use the example with the inline assembler
> code and write a few lines, that these "macros" are no longer supported.

Yes, as part of the cleanups which accompanied the new 'make
headers_install' target for creating sanitised kernel headers, all of
the _syscallX() stuff was removed from user visibility.

Unfortunately, Linus subsequently applied a patch which was sent to him
privately without review on the mailing list, which reverted that fixup
and made _syscallX() visible in userspace again on a couple of
architectures. That regressions should hopefully be fixed again before
2.6.18 is finally released though -- and in fact we're probably going to
kill off _all_ use of _syscallX(), even in the kernel, before 2.6.19.

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