Re: why does fsync() on a tmpfs directory give EINVAL?

[Chris Friesen]

Andrew Morton wrote:
> Chris Friesen <cfriesen@xxxxxxxxxx> wrote:

> > Would a patch that makes it 
> > just return successfully without doing anything be accepted?
>
>
> yup.

Currently tmpfs reuses the simple_dir_operations from libfs.c.

Would it make sense to add the empty fsync() function there, and have 
all other users pick it up as well?  Is this likely to break stuff?

Currently the following code uses simple_dir_operations:

./kernel/cpuset.c
./security/selinux/selinuxfs.c
./ipc/mqueue.c
./include/linux/fs.h
./fs/relayfs/inode.c
./fs/debugfs/inode.c
./fs/ocfs2/dlm/dlmfs.c
./fs/autofs/inode.c
./fs/hugetlbfs/inode.c
./fs/libfs.c
./fs/ramfs/inode.c
./fs/devpts/inode.c
./net/sunrpc/rpc_pipe.c
./mm/shmem.c
./drivers/misc/ibmasm/ibmasmfs.c
./drivers/oprofile/oprofilefs.c
./drivers/isdn/capi/capifs.c
./drivers/usb/core/inode.c
./drivers/usb/gadget/inode.c

Chris

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/