Messages in this thread | | | Date | Thu, 16 Mar 2006 15:58:01 -0800 | From | Andrew Morton <> | Subject | Re: [2.6.16-rc6-m1 PATCH] Connector: Filesystem Events Connector try 2 |
| |
Yi Yang <yang.y.yi@gmail.com> wrote: > > This new patch is update for last patch, it removes spinlock and > makes include/linux/fsnotify.h more clean when CONFIG_FS_EVENTS=n, > it also reformats some too long lines so that they are less than 80 > columns. > > This patch implements a new connector, Filesystem Event Connector, > the user can monitor filesystem activities via it, currently, it > can monitor access, attribute change, open, create, modify, delete, > move and close of any file or directory. > > Every filesystem event will include tgid, uid and gid of the process > which triggered this event, process name, file or directory name > operated by it.
That would seem to have some privacy implications...
I'd expect that all the info which is needed can be obtained via syscall auditing.
I don't recall having seen demand for this feature before. For what reason is it needed? What is the application? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |