From: David Woodhouse <dwmw2@infradead.org>
To: Albert Cahalan <acahalan@gmail.com>
Cc: guest01@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: OT: calling kernel syscall manually
Date: Wed, 13 Sep 2006 07:55:30 +0100 [thread overview]
Message-ID: <1158130530.18619.156.camel@pmac.infradead.org> (raw)
In-Reply-To: <787b0d920609122235j57ac327ckcc8d08832fb3989c@mail.gmail.com>
On Wed, 2006-09-13 at 01:35 -0400, Albert Cahalan wrote:
> > The third one has always been broken on i386 for PIC code
>
> No, I was just using it today in PIC i386 code.
> The %ebx register gets pushed, the needed value
> gets moved into %ebx, the int 0x80 is done, and
> the %ebx register gets popped. Only a few odd
> calls like clone() need something different.
That's a very recent change -- it was broken for years before that.
> > 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.
>
> It's damn useful. Hint: Linux does not require glibc.
Are you being deliberately obtuse or is it just a natural talent?
Other C libraries also provide syscall() -- at least dietlibc and uClibc
do.
Kernel headers do not exist to provide a library of random crap for
userspace to use.
--
dwmw2
next prev parent reply other threads:[~2006-09-13 6:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 5:35 Albert Cahalan
2006-09-13 6:55 ` David Woodhouse [this message]
2006-09-13 15:52 ` Albert Cahalan
-- strict thread matches above, loose matches on Subject: below --
2006-09-12 12:05 guest01
2006-09-12 13:34 ` David Woodhouse
2006-09-12 14:31 ` guest01
2006-09-12 14:37 ` David Woodhouse
2006-09-12 20:25 ` Phillip Susi
2006-09-12 20:46 ` Miguel Ojeda
2006-09-12 22:03 ` Arnd Bergmann
2006-09-12 22:43 ` David Woodhouse
2006-09-13 16:52 ` guest01
2006-09-13 17:52 ` David Woodhouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1158130530.18619.156.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=acahalan@gmail.com \
--cc=guest01@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®