1dnl #
2dnl # 3.5.0 API change
3dnl # torvalds/linux@dbd5768f87ff6fb0a4fe09c4d7b6c4a24de99430 and
4dnl # torvalds/linux@7994e6f7254354e03028a11f98a27bd67dace9f1 reworked
5dnl # where inode_sync_wait() is called.
6dnl #
7dnl # Prior to these changes it would occur in end_writeback() but due
8dnl # to various issues (described in the above commits) it has been
9dnl # moved to evict().   This changes the ordering is which sync occurs
10dnl # but otherwise doesn't impact the zpl implementation.
11dnl #
12dnl # The major impact here is the renaming of end_writeback() to
13dnl # clear_inode().  However, care must be taken when detecting this
14dnl # API change because as recently as 2.6.35 there was a clear_inode()
15dnl # function.  However, it was made obsolete by the evict_inode() API
16dnl # change at the same time.
17dnl #
18dnl # Therefore, to ensure we have the correct API we only allow the
19dnl # clear_inode() compatibility code to be defined iff the evict_inode()
20dnl # functionality is also detected.
21dnl #
22AC_DEFUN([ZFS_AC_KERNEL_SRC_CLEAR_INODE], [
23	ZFS_LINUX_TEST_SRC([clear_inode], [
24		#include <linux/fs.h>
25	], [
26		clear_inode(NULL);
27	])
28])
29
30AC_DEFUN([ZFS_AC_KERNEL_CLEAR_INODE], [
31	AC_MSG_CHECKING([whether clear_inode() is available])
32	ZFS_LINUX_TEST_RESULT_SYMBOL([clear_inode],
33	    [clear_inode], [fs/inode.c], [
34		AC_MSG_RESULT(yes)
35		AC_DEFINE(HAVE_CLEAR_INODE, 1, [clear_inode() is available])
36	], [
37		AC_MSG_RESULT(no)
38	])
39])
40