From: stefan.eletzhofer@eletztrick.de
To: linux-kernel@vger.kernel.org
Subject: Re: Syscall table AKA hijacking syscalls
Date: Wed, 7 Jan 2004 10:28:32 +0100 [thread overview]
Message-ID: <20040107092832.GA450@gonzo.local> (raw)
In-Reply-To: <3FF59073.3060305@conet.cz>
On Fri, Jan 02, 2004 at 04:38:27PM +0100, Libor Vanek wrote:
>
> >>I'm writing some project which needs to hijack some syscalls in VFS
> >>layer. AFAIK in 2.6 is this "not-wanted" solution (even that there are
> >>some very nasty ways of doing it - see
> >>http://mail.nl.linux.org/kernelnewbies/2002-12/msg00266.html )
> >>
> >>
> >
> >Why do you need to hijack system calls from a module? 99% of the
> >times, it's the wrong technical solution.
> >
> >
> I'm working on my diploma thesis which is adding snapshot capability
> into Linux VFS (so you can do directory based snapshots - not complete
> device, like in LVM). It'll consist of two separete modules:
> Snapshot module:
> - will hijack (one or another way) calls to open/move/unlink/mkdir/etc.
> syscall
> - when will detect change to selected directory (which I want to
> snapshot), it'll copy/move old file/directory to some temporary
> (selected when creating snapshot) - in fact - copy on write behaviour
Do it in userspace. Hack a nfs server.
>
> UnionFS module:
> - will place "temporary" directory with saved files/dirs "over" actual
> one and result will be read-only snapshot - this can be done without
> hijacking syscalls probably
> - something like overlay fs but a bit different
>
> --
>
> Libor Vanek
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Eletztrick Computing - Customized Linux Development
Stefan Eletzhofer, Marktstrasse 43, DE-88214 Ravensburg
http://www.eletztrick.de
next prev parent reply other threads:[~2004-01-07 9:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 12:59 Syscall table AKA hijacking syscalls Libor Vanek
2004-01-02 13:08 ` Matti Aarnio
2004-01-02 13:26 ` Libor Vanek
2004-01-02 13:57 ` Ragnar Kjørstad
2004-01-02 15:39 ` Libor Vanek
2004-01-02 16:42 ` Jörn Engel
2004-01-02 15:12 ` Muli Ben-Yehuda
2004-01-02 15:38 ` Libor Vanek
2004-01-02 16:00 ` Christoph Hellwig
2004-01-02 16:35 ` Jörn Engel
2004-01-02 16:59 ` Libor Vanek
2004-01-02 18:04 ` Jörn Engel
2004-01-02 18:58 ` Libor Vanek
2004-01-02 19:15 ` Arjan van de Ven
2004-01-02 19:23 ` Libor Vanek
2004-01-02 19:18 ` Jörn Engel
2004-01-02 19:37 ` Libor Vanek
2004-01-02 19:56 ` Jörn Engel
2004-01-07 9:28 ` stefan.eletzhofer [this message]
2004-01-02 23:35 ` Anton Blanchard
2004-01-02 23:46 ` Libor Vanek
2004-01-03 15:41 ` Helge Hafting
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=20040107092832.GA450@gonzo.local \
--to=stefan.eletzhofer@eletztrick.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.