diff options
author | Richard Yao <[email protected]> | 2012-07-23 11:11:25 -0700 |
---|---|---|
committer | Brian Behlendorf <[email protected]> | 2012-07-23 12:29:32 -0700 |
commit | ea1fdf46e2d37e9eb048f9add0fb06e77e9ee6e2 (patch) | |
tree | be21fa4bb6f934868c4ffe29a48eba6dcbe71613 /config/kernel-truncate-range.m4 | |
parent | 756c3e5a9ce36461939a8dc421918e1c3a379fa6 (diff) |
Linux 3.5 compat, iops->truncate_range() removed
The vmtruncate_range() support has been removed from the kernel in
favor of using the fallocate method in the file_operations table.
Signed-off-by: Richard Yao <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Issue #784
Diffstat (limited to 'config/kernel-truncate-range.m4')
-rw-r--r-- | config/kernel-truncate-range.m4 | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/config/kernel-truncate-range.m4 b/config/kernel-truncate-range.m4 new file mode 100644 index 000000000..da2cb50fc --- /dev/null +++ b/config/kernel-truncate-range.m4 @@ -0,0 +1,24 @@ +dnl # +dnl # 3.5.0 API change +dnl # torvalds/linux@17cf28afea2a1112f240a3a2da8af883be024811 removed +dnl # truncate_range(). The file hole punching functionality is now +dnl # provided by fallocate() +dnl # +AC_DEFUN([ZFS_AC_KERNEL_TRUNCATE_RANGE], [ + AC_MSG_CHECKING([whether iops->truncate_range() exists]) + ZFS_LINUX_TRY_COMPILE([ + #include <linux/fs.h> + void truncate_range(struct inode *inode, loff_t start, + loff_t end) { return; } + static struct inode_operations iops __attribute__ ((unused)) = { + .truncate_range = truncate_range, + }; + ],[ + ],[ + AC_MSG_RESULT(yes) + AC_DEFINE(HAVE_INODE_TRUNCATE_RANGE, 1, + [iops->truncate_range() exists]) + ],[ + AC_MSG_RESULT(no) + ]) +]) |