Whamcloud - gitweb
LU-6215 llite: handle backing_dev_info removal 82/15182/4
authorJames Simmons <uja.ornl@yahoo.com>
Tue, 11 Aug 2015 15:33:17 +0000 (11:33 -0400)
committerOleg Drokin <oleg.drokin@intel.com>
Wed, 19 Aug 2015 15:59:10 +0000 (15:59 +0000)
commit7e0e87e6f2dbd04e6fb94123f453ad8f2806dc8b
treeccf1f249197337ac3e7a56e4f839ac73a2cc9c4f
parent1bf48948a99f51ede84a467a23c59c55eb055d7b
LU-6215 llite: handle backing_dev_info removal

For kernels before 3.20 the struct address_space contained
a pointer to a struct backing_dev_info. This backing_dev_info
had to setup with the backing_dev_info that was contained
in the super block. Now in newer kernels that backing_dev_info
pointer has been removed from the address_space. If you want
to use the backing_dev_info you need to access it from the
super block data structure directly. Lustre upstream removed
all the backing_dev_info setup for the inode i_mapping which
is no longer needed. This patch makes Lustre handle the bdi
inode backing_dev_info only for per 3.20 kernels now. This
change was due to:

Linux-commit: 6bec0035286119eefc32a5b1102127e6a4032cb2

Another change in the 3.20 kernels is the removal of the mmap
functionaly for the backing device. This was removed in with

Linux-commit: b4caecd48005fbed3949dde6c1cb233142fd69e9

With this change the flag BDI_CAP_MAP_COPY was removed.

Signed-off-by: James Simmons <uja.ornl@yahoo.com>
Change-Id: Ic2cd9227c99e3f66001ea9470cdc6bfdbf4f1c2c
Reviewed-on: http://review.whamcloud.com/15182
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/llite_lib.c