linux-toradex.git/include/linux/fsnotify.h, branch v2.6.38.6

fs: dcache remove dcache_lock

2011-01-07T06:50:23+00:00

dcache_lock no longer protects anything. remove it.

Signed-off-by: Nick Piggin

fanotify: if set by user unset FMODE_NONOTIFY before fsnotify_perm() is called

2010-12-07T21:14:21+00:00

Unsetting FMODE_NONOTIFY in fsnotify_open() is too late, since fsnotify_perm()
is called before. If FMODE_NONOTIFY is set fsnotify_perm() will skip permission
checks, so a user can still disable permission checks by setting this flag
in an open() call.
This patch corrects this by unsetting the flag before fsnotify_perm is called.

Signed-off-by: Lino Sanfilippo 
Signed-off-by: Eric Paris

Ensure FMODE_NONOTIFY is not set by userspace

2010-10-30T18:07:40+00:00

    In fsnotify_open() ensure that FMODE_NONOTIFY is never set by userspace.
    Also always call fsnotify_parent and fsnotify.

Signed-off-by: Lino Sanfilippo 
Signed-off-by: Eric Paris

fsnotify: rename FS_IN_ISDIR to FS_ISDIR

2010-10-28T21:22:15+00:00

The _IN_ in the naming is reserved for flags only used by inotify.  Since I
am about to use this flag for fanotify rename it to be generic like the
rest.

Signed-off-by: Eric Paris

fsnotify: call fsnotify_parent in perm events

2010-10-28T21:22:13+00:00

fsnotify perm events do not call fsnotify parent.  That means you cannot
register a perm event on a directory and enforce permissions on all inodes in
that directory.  This patch fixes that situation.

Signed-off-by: Eric Paris

Revert "fsnotify: store struct file not struct path"

2010-08-12T21:23:04+00:00

This reverts commit 3bcf3860a4ff9bbc522820b4b765e65e4deceb3e (and the
accompanying commit c1e5c954020e "vfs/fsnotify: fsnotify_close can delay
the final work in fput" that was a horribly ugly hack to make it work at
all).

The 'struct file' approach not only causes that disgusting hack, it
somehow breaks pulseaudio, probably due to some other subtlety with
f_count handling.

Fix up various conflicts due to later fsnotify work.

Signed-off-by: Linus Torvalds

fsnotify: store struct file not struct path

2010-07-28T14:18:51+00:00

Al explains that calling dentry_open() with a mnt/dentry pair is only
garunteed to be safe if they are already used in an open struct file.  To
make sure this is the case don't store and use a struct path in fsnotify,
always use a struct file.

Signed-off-by: Eric Paris

fsnotify: initialize mask in fsnotify_perm

2010-07-28T13:59:02+00:00

akpm got a warning the fsnotify_mask could be used uninitialized in
fsnotify_perm().  It's not actually possible but his compiler complained
about it.  This patch just initializes it to 0 to shut up the compiler.

Reported-by: Andrew Morton 
Signed-off-by: Eric Paris

fsnotify: new fsnotify hooks and events types for access decisions

2010-07-28T13:59:01+00:00

introduce a new fsnotify hook, fsnotify_perm(), which is called from the
security code.  This hook is used to allow fsnotify groups to make access
control decisions about events on the system.  We also must change the
generic fsnotify function to return an error code if we intend these hooks
to be in any way useful.

Signed-off-by: Eric Paris

fsnotify: use unsigned char * for dentry->d_name.name

2010-07-28T13:59:01+00:00

fsnotify was using char * when it passed around the d_name.name string
internally but it is actually an unsigned char *.  This patch switches
fsnotify to use unsigned and should silence some pointer signess warnings
which have popped out of xfs.  I do not add -Wpointer-sign to the fsnotify
code as there are still issues with kstrdup and strlen which would pop
out needless warnings.

Signed-off-by: Eric Paris