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

Message-ID: <4506C4D3.7030304@gmail.com>
Date:	Tue, 12 Sep 2006 16:31:47 +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:
> The third one has always been broken on i386 for PIC code and was
> pointless anyway, since glibc provides this functionality. The kernel
> method has been removed from userspace visibility all architectures, and
> we plan to remove it entirely in 2.6.19 since it's not at all useful. 
> 
> However, there was a patch which was sneaked to Linus in private which
> reverted that cleanup on i386 and x86_64 and made them visible again --
> but they'll be going away again on those two architectures shortly;
> hopefully before 2.6.18.
> 
> Don't bother with it -- just use glibc's syscall().
> 

Thx for the fast reply. I wouldn't use the third method (3 -> using
kernel directly) in one of my projects, but I have to try each one of
the three methods for a small assignment (unfortunately, not every
assignment is very useful at a university :-))
So, I would be very grateful if you have some code snippets or further
information for me about method #3.

thx again
regards
Peda


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