diff options
| author | Boaz Harrosh <Boaz Harrosh bharrosh@panasas.com> | 2010-10-07 14:28:18 -0400 |
|---|---|---|
| committer | Boaz Harrosh <bharrosh@panasas.com> | 2010-10-18 20:16:02 +0200 |
| commit | 115e19c53501edc11f730191f7f047736815ae3d (patch) | |
| tree | eddb72bc6ed53acf0bba8a98ebbda438b63997ae /fs/exofs | |
| parent | 7aebf4106b4263667696485303af498aa1eea9ef (diff) | |
exofs: Set i_mapping->backing_dev_info anyway
Though it has been promised that inode->i_mapping->backing_dev_info
is not used and the supporting code is fine. Until the pointer
will default to NULL, I'd rather it points to the correct thing
regardless.
At least for future infrastructure coder it is a clear indication
of where are the key points that inodes are initialized.
I know because it took me time to find this out.
Signed-off-by: Boaz Harrosh <Boaz Harrosh bharrosh@panasas.com>
Diffstat (limited to 'fs/exofs')
| -rw-r--r-- | fs/exofs/inode.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/fs/exofs/inode.c b/fs/exofs/inode.c index 24ab327a20c..0ba9886da2e 100644 --- a/fs/exofs/inode.c +++ b/fs/exofs/inode.c @@ -1030,6 +1030,7 @@ 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; @@ -1129,6 +1130,7 @@ 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++; |