projects/linux·commit 0b0abeaf

Revert "exofs: Set i_mapping->backing_dev_info anyway"

0b0abeaf · Boaz Harrosh <[email protected]> · 2011-02-02 21:02:12 +02:00

This reverts commit 115e19c53501edc11f730191f7f047736815ae3d.

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 [email protected] as well, since it exists also in
2.6.37.  2.6.36 is good and does not have this patch.

CC: Stable Tree <[email protected]>
Signed-off-by: Boaz Harrosh <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Commit
0b0abeaf3d30cec03ac6497fe978b8f7edecc5ae
Parents
f2f1756d

Changes

1 files changed · +0 −2

FileStatusAddDelContent
fs/exofs/inode.cmodified+0−2View file

fs/exofs/inode.c

View file
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++;