[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOh0hwPbV5=QU=bB6Atw5taGW8CN9r8UesE=ZhKrO+sRDY0_3A@mail.gmail.com>
Date: Fri, 23 Dec 2011 15:20:35 +0530
From: Gaurav Saxena <grvsaxena419@...il.com>
To: Jiri Kosina <jkosina@...e.cz>
Cc: linux-kernel@...r.kernel.org
Subject: Re: Intercepting system calls
Hello Jiri
On Fri, Dec 23, 2011 at 3:17 PM, Jiri Kosina <jkosina@...e.cz> wrote:
> On Thu, 22 Dec 2011, Gaurav Saxena wrote:
>
>> I am writing an application for which I need to intercept some
>> filesystem system calls eg. unlink. I need unlink to call my code
>> before deleting abc so that I could probably prevent unlink . I would
>> like to implement this in a kernel module instead of modifying kernel
>> code itself. I would like to intercept system calls by replacing
>> system calls but I have not been able to find any method of doing that
>> in linux > 3.0. Please suggest some method of doing that.
>
> Write a kernel module that instruments sys_unlink() via krpobes. See
> Documentation/kprobes.txt for details.
Ok. I am looking at its details, will try that. But how could a probe
prevent execution of a system call?
>
> --
> Jiri Kosina
> SUSE Labs
>
--
Thanks and Regards ,
Gaurav
--
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/
Powered by blists - more mailing lists