mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: guest01 <guest01@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OT: calling kernel syscall manually
Date: Tue, 12 Sep 2006 14:34:04 +0100	[thread overview]
Message-ID: <1158068045.9189.93.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <4506A295.6010206@gmail.com>

On Tue, 2006-09-12 at 14:05 +0200, guest01 wrote:
> Hi
> 
> Sorry guys, this question is a little bit off topic, but maybe someone
> has an answer, I am sure that there is a simple one. :-)
> 
> Ok, I have to find 3 possibilities to create a directory with 3 small c
> programs:
> 1 -> using libc: mkdir(dir,mode)
> 2 -> using libcsyscall:  syscall(__NR_mkdir, "mkdirLibcSyscall", 0777);
> 3 -> using kernel directly
> 
> Ok, the third one is a little bit tricky, at least for me. I found an
> example for lseek, but I don't know how to convert that for mkdir. I
> don't know the necessary arguments, ..

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().

-- 
dwmw2


  reply	other threads:[~2006-09-12 13:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12 12:05 guest01
2006-09-12 13:34 ` David Woodhouse [this message]
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
2006-09-13  5:35 Albert Cahalan
2006-09-13  6:55 ` David Woodhouse
2006-09-13 15:52   ` Albert Cahalan

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=1158068045.9189.93.camel@hades.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --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®