From: devzero@web.de
To: linux-fsdevel@vger.kernel.org
Subject: tracing at filesystem level
Date: Fri, 21 Nov 2008 16:53:40 +0100 [thread overview]
Message-ID: <515126840@web.de> (raw)
Hello,
i`d like to be able to trace filesystem access at early boot time, i.e to see what files being opened/closed on early boot (and later on).
one possible way to do it is using nfs-root, so we can trace it at the network or server level - but how can this be done without using network filesystem ?
i came across tracefs (http://www.filesystems.org/docs/tracefs-fast04/tracefs.pdf) which looks very promising, but it seems it`s not actively maintained.
isn`t there a standard way to do that with recent kernels ?
i searched for a while but didn`t find something appropriate....
regards
Roland
ps:
this is also very interesting for intrusion detection - think of virtual machine`s filesystem activity being watched trough serial console (i.e.
with nothing running in userspace and without hackers ability to disable it)
____________________________________________________________________
Psssst! Schon vom neuen WEB.DE MultiMessenger gehört?
Der kann`s mit allen: http://www.produkte.web.de/messenger/?did=3123
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2008-11-21 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 15:53 devzero [this message]
2008-11-22 7:50 ` tracing at filesystem level Francis Moreau
-- strict thread matches above, loose matches on Subject: below --
2008-11-22 13:58 devzero
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=515126840@web.de \
--to=devzero@web.de \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).