Whamcloud - gitweb
LU-6215 llite: handle new_sync_[read|write] removal 65/15165/5
authorJames Simmons <uja.ornl@yahoo.com>
Thu, 30 Jul 2015 16:04:41 +0000 (12:04 -0400)
committerOleg Drokin <oleg.drokin@intel.com>
Sun, 9 Aug 2015 23:40:33 +0000 (23:40 +0000)
commit0c080f1e8791b6b1aebba9d2165235122697db68
treef1bbdfa036616edac87119f3ab871dd08981ed28
parentfc2f0c39d8bed5060774e3b4cca7bf13faa3692a
LU-6215 llite: handle new_sync_[read|write] removal

In newer linux kernel version the file read/write
API have been moving to using struct iov_iter. To
continue supporting the old API new wrapper
functions were created, new_sync_*, which allowed
the use of the new API's to support the old API's.
For the linux 4.1 kernel those new_sync_* are used
internally so they are no longer exposed to any
file systems. If a file system wants to use the
"old" api they need to call vfs_[write|read].
Update lustre to handle this change. The upstream
commit that made new_sync_* internal was:

Linux commit: 5d5d568975307877e9195f5305f4240e506a2807

Signed-off-by: James Simmons <uja.ornl@yahoo.com>
Change-Id: Ibf69d25af8a7d5cda00c5b1be4757ec369e8e814
Reviewed-on: http://review.whamcloud.com/15165
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Bob Glossman <bob.glossman@intel.com>
Reviewed-by: Dmitry Eremin <dmitry.eremin@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
lustre/autoconf/lustre-core.m4
lustre/llite/file.c