From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Reading from file in module fails
Date: Mon, 3 May 2004 14:41:05 +0200 [thread overview]
Message-ID: <20040503124105.GS29503@lug-owl.de> (raw)
In-Reply-To: <20040503114316.GA22732@Loki>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
On Mon, 2004-05-03 13:43:16 +0200, Libor Vanek <libor@conet.cz>
wrote in message <20040503114316.GA22732@Loki>:
> It's not bad design - what I'm doing is writing snapshots for VFS as my diploma thesis. And I need to create copy of file before it's changed (copy-on-write). There is no other way how to do it in kernel-space (and user-space solutions like using LUFS are really slow)
That can all be done in userspace.
$ export LD_PRELOAD=libcopyfilesbeforemodify.so
You just need to program a library that provides all functions that
modify files (eg. write, open with O_CREAT, ...) and you're done - 100%
in userspace.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-03 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 10:50 Reading from file in module fails Libor Vanek
2004-05-03 11:35 ` Erik Mouw
2004-05-03 11:43 ` Libor Vanek
2004-05-03 11:48 ` Erik Mouw
2004-05-03 12:07 ` root
2004-05-03 12:41 ` Jan-Benedict Glaw [this message]
[not found] <1RJl8-Eo-5@gated-at.bofh.it>
[not found] ` <1RJXT-19T-37@gated-at.bofh.it>
[not found] ` <1RK7v-1gJ-9@gated-at.bofh.it>
[not found] ` <1RL3A-23k-23@gated-at.bofh.it>
2004-05-03 16:55 ` Pascal Schmidt
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=20040503124105.GS29503@lug-owl.de \
--to=jbglaw@lug-owl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox