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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <45083731.7040904@gmail.com>
Date:	Wed, 13 Sep 2006 18:52:01 +0200
From:	guest01 <guest01@...il.com>
To:	David Woodhouse <dwmw2@...radead.org>
CC:	linux-kernel@...r.kernel.org
Subject: Re: OT: calling kernel syscall manually

David Woodhouse wrote:
> However, the _example_ that the OP gave of this 'third one' was in fact
> using the old _syscallX() macros which used to be found in the kernel's
> private header files. So I assumed that's what he meant, rather than
> open-coding his own inline assembly.
> 

Yes, indeed. I think we should use the _syscallX() macro, but
nevertheless I like the inline assembly example :-)

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.

thxs


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