[PATCH] Revert "exofs: Set i_mapping->backing_dev_info anyway"

[PATCH] Revert "exofs: Set i_mapping->backing_dev_info anyway"

[Boaz Harrosh]

This reverts commit 115e19c53501edc11f730191f7f047736815ae3d
	exofs: Set i_mapping->backing_dev_info anyway

Apparently setting inode->bdi to one's own sb->s_bdi stops
VFS from sending *read-aheads*. This problem was bisected
to this commit. A revert fixes it. I'll investigate farther
why is this happening for the next Kernel, but for now a revert.

I'm sending to stable@kernel.org as well, since it exists also
in 2.6.37.
2.6.36 is good and does not have this patch.

CC: Stable Tree <stable@kernel.org>
Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
---
 fs/exofs/inode.c |    2 --
 1 files changed, 0 insertions(+), 2 deletions(-)

diff --git a/fs/exofs/inode.c b/fs/exofs/inode.c
index 4268542..a755523 100644
--- a/fs/exofs/inode.c
+++ b/fs/exofs/inode.c
@@ -1030,7 +1030,6 @@ struct inode *exofs_iget(struct super_block *sb, unsigned long ino)
 		memcpy(oi->i_data, fcb.i_data, sizeof(fcb.i_data));
 	}
 
-	inode->i_mapping->backing_dev_info = sb->s_bdi;
 	if (S_ISREG(inode->i_mode)) {
 		inode->i_op = &exofs_file_inode_operations;
 		inode->i_fop = &exofs_file_operations;
@@ -1131,7 +1130,6 @@ struct inode *exofs_new_inode(struct inode *dir, int mode)
 
 	sbi = sb->s_fs_info;
 
-	inode->i_mapping->backing_dev_info = sb->s_bdi;
 	sb->s_dirt = 1;
 	inode_init_owner(inode, dir, mode);
 	inode->i_ino = sbi->s_nextid++;
-- 
1.7.2.3