All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Davis <reiser-list@empires.org>
To: reiserfs-list@namesys.com
Subject: reiser4 as module
Date: Wed, 21 Jul 2004 19:00:47 -0700	[thread overview]
Message-ID: <1090461647.1676.16.camel@jeff> (raw)
In-Reply-To: <20040721231748.46066.qmail@web60310.mail.yahoo.com>

Using 2.6.5-rc with the all.diff.gz patch on the website.

I am trying to develop my own plugin. I think I got a good start, I
added an extra built-in pseudo file. However, it's slow going because I
have to reboot to test my code.

I tried compiling reiser4 as a module, but if I "rmmod reiser4" then
change the code, then "make modules && make modules_install", then
"modprobe reiser4", then I get a seg fault. After that the reiser4
module is stuck (says it's in use) and I can't use reiser4 at all after
I do that, until I reboot.

Does someone have a better suggestion for me? Is the unloading of
reiser4 problem a bug? Am I not doing it correctly (this is my first
kernel modification)?

As a seperate issue, the plugin I'm trying to ultimately create is one
where you can access a script by doing something like
"/path/to/script.py/pyexe" and it would execute the script and the file
contents would be (read only) the stdout. That would allow cool stuff
like having a configuration file be just data pulled from a database (as
an example). Is this even possible? I'm still trying to figure out how
I'd write it in a secure way (we don't want to execute a user's script
in kernel address space).

	Regards,
		Jeff Davis

P.S. Nice code! The parts I saw were very easy to read and modify.


  reply	other threads:[~2004-07-22  2:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-21 23:17 rip? Dirk Wetter
2004-07-22  2:00 ` Jeff Davis [this message]
2004-07-22  3:50   ` reiser4 as module David Masover
2004-07-22  4:22     ` Jeff Davis
2004-07-22 10:13       ` mjt

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=1090461647.1676.16.camel@jeff \
    --to=reiser-list@empires.org \
    --cc=reiserfs-list@namesys.com \
    /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.