From: Libor Vanek <libor@conet.cz>
To: linux-kernel@vger.kernel.org
Subject: Syscall table AKA hijacking syscalls
Date: Fri, 02 Jan 2004 13:59:08 +0100 [thread overview]
Message-ID: <3FF56B1C.1040308@conet.cz> (raw)
Hi,
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 )
Also I've found out that Linus stated that intercepting syscalls is "bad
thing" (load module a, load module b, unload module b => crash) but I
think that there are some very good reasons (and ways) to do it (see
http://syscalltrack.sourceforge.net ). My main reason to do it is that I
want my GPLed module to be able to modify some VFS syscalls without
patching and recompiling whole kernel and rebooting the machine.
So what is proper (Linus recommanded) way to do such a things? Create
patches for specific syscalls like "if this_module_installed then
call_this_function;" or try to force things like syscalltrack to go into
vanilla kernel some time? Because what I've found out there are more
projects which suffer from this restriction.
--
Libor Vanek
next reply other threads:[~2004-01-02 12:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 12:59 Libor Vanek [this message]
2004-01-02 13:08 ` Syscall table AKA hijacking syscalls 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
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=3FF56B1C.1040308@conet.cz \
--to=libor@conet.cz \
--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