[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Dazuko-devel] Device file events

From: Abhishek Nayani
Subject: Re: [Dazuko-devel] Device file events
Date: Tue, 13 Sep 2005 22:12:47 -0600


I understood what you meant by "many". Our requirement involves
monitoring of 
dev nodes which are being filtered out here. May I suggest the filter
be changed to
some thing more like:

     if (S_ISDIR(xfs->inode->i_mode))
        return 0;
Instead of just allowing files and links. The above snippet will take
care of decreasing 
directory access events and also allow block and char devices to be

One more question, since we are going to be using DazukoFS (a stackable
fs) in the next
release, I tried a simple feasibility exercise. Using FIST I generated
a wrapper file system 
which just forwards all VFS functions to the fs below it. When I
mounted this wrapfs on top
of root, I was able to see all the files under root but the files under
child mounts like /usr and
/home (which were mounted on different partitions) disappeared. Since
whatever fs we stack,
cannot override the path_lookup for other filesystems, is there a way
to do it ? and has this been
considered ?

>>> John Ogness <address@hidden> 09/13/05 7:33 pm >>> 
Abhishek Nayani wrote:
> Currently, Dazuko only supports "Open" and "Exec" events on 2.6 using
LSM. Since dazuko registers the "inode_permission" hook, all the events
which are generated are because of open or exec, which are what we need.
Can you expand on what you mean by "many" events ?

I have included a simple patch that will allow all the file types to
generate events. I recommend that you try it out and see how many
(particularly directory events) are generated. Then you will understand
I mean by "many".

> Also, the context switches happen only when the user registers for
the dev directory, so I guess they do not come into the picture unless
the user actually wants to listen to them.

Yes, you are correct.

If you try allowing all file types, you will see the number events. I
this alarming (and a bit misleading for the registered application), so
decided to filter out all non- file or non- link events.

John Ogness

Dazuko Maintainer

reply via email to

[Prev in Thread] Current Thread [Next in Thread]