[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOh0hwPeveaEaNv_mjNVLM36JSbObX4n5y1jC_Yp5MwdBA0Sxw@mail.gmail.com>
Date: Fri, 23 Dec 2011 07:52:59 +0530
From: Gaurav Saxena <grvsaxena419@...il.com>
To: John Stoffel <john@...ffel.org>
Cc: richard -rw- weinberger <richard.weinberger@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: Intercepting system calls
Hello John,
On Thu, Dec 22, 2011 at 11:22 PM, John Stoffel <john@...ffel.org> wrote:
>>>>>> "Gaurav" == Gaurav Saxena <grvsaxena419@...il.com> writes:
>
>>> Intercepting system calls is very bad, don't do it.
>
> Gaurav> Oh. I will not do it then, could you suggest me something so
> Gaurav> that I could prevent unlink on some file say using kernel
> Gaurav> support. I want to save file on unlink how could I do that
> Gaurav> without kernel support, or how could I do that using a kernel
> Gaurav> module.
>
> Write a FUSE module to mount the filesystem through, inside your FUSE
> module you can intercept the unlink/truncate/write calls and decide
> what you want to have happen.
>
> John
I would like to write it differently for each type of filesystem ?
Because what operations to call after my function depends on this.
Also Can I mount "/" in this way ?
--
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