Directory writes are synchronous, so this is fine. There's a
mostly-convenient function in fs/libfs.c that returns 0 that we can use
to do what we want ("mostly" because it was renamed in 2.6.35).
FIXES 130425
Change-Id: I9a2af60ed3152be036f0145c94152d8cff2e1242
Reviewed-on: http://gerrit.openafs.org/6491
Reviewed-by: Simon Wilkinson <sxw@inf.ed.ac.uk>
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Derrick Brashear <shadow@dementix.org>
AC_CHECK_LINUX_FUNC([zero_user_segments],
[#include <linux/highmem.h>],
[zero_user_segments(NULL, 0, 0, 0, 0);])
+ AC_CHECK_LINUX_FUNC([noop_fsync],
+ [#include <linux/fs.h>],
+ [noop_fsync(NULL, 0, 0, 0);])
dnl Consequences - things which get set as a result of the
dnl above tests
.open = afs_linux_open,
.release = afs_linux_release,
.llseek = default_llseek,
+#ifdef HAVE_LINUX_NOOP_FSYNC
+ .fsync = noop_fsync,
+#else
+ .fsync = simple_sync_file,
+#endif
};
struct file_operations afs_file_fops = {