From: Steven Rostedt <rostedt@goodmis.org>
To: selvakumar nagendran <kernelselva@yahoo.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Intercepting system calls
Date: Tue, 21 Dec 2004 08:51:23 -0500 [thread overview]
Message-ID: <1103637083.17511.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20041221042224.48160.qmail@web60608.mail.yahoo.com>
On Mon, 2004-12-20 at 20:22 -0800, selvakumar nagendran wrote:
> I want to intercept system calls that are provided
> for IPC in Linux. I have to determine whether a
> process blocks while executing a system call and I
> must save the arguments passed to that system call.
> Can I modify the system call source code directly
> for this? or if I want the system calls to refer my
> module, how should I do that? can anyone explain for
> this, if possible with some code?..
Do you have to do this in the kernel? Have you taken a look at ptrace?
Especially PTRACE_SYSCALL (man ptrace). Although it may be trickier to
know if it blocked or not, but it should still be possible to do
entirely from user land, and thus easier to write/debug.
-- Steve
next prev parent reply other threads:[~2004-12-21 13:51 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 4:22 Intercepting system calls selvakumar nagendran
2004-12-21 4:28 ` Lee Revell
2004-12-21 13:51 ` Steven Rostedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-04 19:00 Oleg Kutkov
2010-02-04 19:26 ` Bryan Donlan
[not found] ` <5e9821061002042140le7ba356s48e535c9d8b637ec@mail.gmail.com>
2010-02-05 7:20 ` Bryan Donlan
2011-12-22 16:07 Gaurav Saxena
2011-12-22 16:42 ` richard -rw- weinberger
2011-12-22 16:59 ` Gaurav Saxena
2011-12-22 17:05 ` richard -rw- weinberger
2011-12-22 17:16 ` Gaurav Saxena
2011-12-22 17:32 ` richard -rw- weinberger
2011-12-22 17:37 ` Gaurav Saxena
2011-12-22 17:52 ` John Stoffel
2011-12-23 2:22 ` Gaurav Saxena
2011-12-23 14:38 ` John Stoffel
2011-12-23 17:03 ` Gaurav Saxena
2011-12-28 12:56 ` Wojciech Zygmunt Porczyk
2011-12-29 6:38 ` Gaurav Saxena
2011-12-23 14:50 ` Alan Cox
2011-12-23 17:07 ` Gaurav Saxena
2011-12-22 19:03 ` Wakko Warner
2011-12-23 2:25 ` Gaurav Saxena
2011-12-23 9:45 ` Jiri Kosina
2011-12-23 15:10 ` Wakko Warner
2011-12-23 7:25 ` J. R. Okajima
2011-12-23 9:08 ` Gaurav Saxena
2011-12-23 9:16 ` richard -rw- weinberger
2011-12-23 9:22 ` Gaurav Saxena
2011-12-23 9:26 ` richard -rw- weinberger
2011-12-23 9:37 ` Gaurav Saxena
2011-12-23 9:47 ` Jiri Kosina
2011-12-23 9:50 ` Gaurav Saxena
2011-12-23 11:59 ` Gaurav Saxena
2011-12-23 12:29 ` Maxin B John
2011-12-23 12:50 ` Gaurav Saxena
2011-12-23 13:00 ` richard -rw- weinberger
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=1103637083.17511.3.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=kernelselva@yahoo.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;
as well as URLs for NNTP newsgroup(s).