From: Stephan Menzel <stephan42@chinguarime.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [FS] New monitor framework in 2.6.10?
Date: Mon, 15 Nov 2004 11:42:33 +0100 [thread overview]
Message-ID: <200411151142.33640.stephan42@chinguarime.net> (raw)
In-Reply-To: <Pine.LNX.4.53.0411151121240.6893@yvahk01.tjqt.qr>
Am Montag, 15. November 2004 11:23 schrieb Jan Engelhardt:
> > will be exactly for this kind of purpose. Some kind of monitor frameworks
> > that can generate events for all sorts of things. Sorry, I don't know any
> > more about it.
>
> Wasnot it called System Call Auditing and/or Filesystem hooks?
Well, that's what I'd like to know.
System Call Auditing just yielded a few google results but it doesn't seem to
me like a well documented feature. More like people asking for it.
> One or the other was present in SUSE's 2.4.20/.21 kernels and one is in
> 2.6.x -- and from what I have seen, they're just hooks, i.e.
>
> if(hook != NULL) { hook(fd, buf, size); }
>
> That's the most efficient thing you can have (in a function). It's only a
> question whether it is in the right function, then.
Indeed.
And just that made me hope there is something like an auditing or monitoring
framework just like for instance a accessible struct with several function
pointers where one could insert funtions to be processed whenever event x
occurs. This kind of thing yould be maintained by the kernel developers who
could put the hook just in the right place and the 'user' (which would be me
in that case) could be sure that his function would be called in the right
time and from the right place.
That would be nice.
Greetings...
Stephan
next prev parent reply other threads:[~2004-11-15 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 10:13 Stephan Menzel
2004-11-15 10:23 ` Jan Engelhardt
2004-11-15 10:42 ` Stephan Menzel [this message]
2004-11-15 12:44 ` Stephan Menzel
2004-11-15 13:29 ` Paolo Ciarrocchi
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=200411151142.33640.stephan42@chinguarime.net \
--to=stephan42@chinguarime.net \
--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
all inboxes | Powered by JetHome®