From: Joshua Roys <TheReader06@comcast.net>
To: linux-assembly@vger.kernel.org
Subject: Re: sources of linux 'system call'
Date: Sat, 08 Sep 2007 12:40:28 -0400 [thread overview]
Message-ID: <46E2D07C.5010006@comcast.net> (raw)
In-Reply-To: <478396.28358.qm@web50305.mail.re2.yahoo.com>
Lukas wrote:
> Hi.
> I'm looking for sources of system calls.
> I mean ... what program is exeecute after I call 'int
> $0x80' :), for example
>
> movq $125,%rax # call sys_mprotect
> movq $smc_address,%rbx
> movq $0x1000,%rcx
> movq $7,%rdx
> int $0x80
>
> ?????????????????
> ?????????????????
>
> i want to ask if enybody knows where can i find it
> (they should be somewhere in kernale source, but i
> couldn't find it)
>
> Regards
> Lukas
>
Hi,
Do something like:
~/sources/linux-2.6.22.y> find . -type f -exec grep -H sys_open \{} \;
for the open system call code.. they're all over the place, the system
calls.
sys_open, for example, is in fs/open.c
Good luck,
Joshua Roys
next prev parent reply other threads:[~2007-09-08 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 16:08 sources of linux 'system call' Lukas
2007-09-08 16:40 ` Joshua Roys [this message]
2007-09-13 17:52 ` Lukas
2007-09-13 18:47 ` Joshua Roys
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=46E2D07C.5010006@comcast.net \
--to=thereader06@comcast.net \
--cc=linux-assembly@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;
as well as URLs for NNTP newsgroup(s).