[PATCH 05/12] block_dev: get bdev inode bdi directly from the block device
Jan Kara
jack at suse.cz
Wed Jan 14 05:00:21 PST 2015
On Wed 14-01-15 10:42:34, Christoph Hellwig wrote:
> Directly grab the backing_dev_info from the request_queue instead of
> detouring through the address_space.
>
> Signed-off-by: Christoph Hellwig <hch at lst.de>
> Reviewed-by: Tejun Heo <tj at kernel.org>
Looks good. You can add:
Reviewed-by: Jan Kara <jack at suse.cz>
Honza
> ---
> fs/fs-writeback.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
> index 2d609a5..e8116a4 100644
> --- a/fs/fs-writeback.c
> +++ b/fs/fs-writeback.c
> @@ -69,10 +69,10 @@ EXPORT_SYMBOL(writeback_in_progress);
> static inline struct backing_dev_info *inode_to_bdi(struct inode *inode)
> {
> struct super_block *sb = inode->i_sb;
> -
> +#ifdef CONFIG_BLOCK
> if (sb_is_blkdev_sb(sb))
> - return inode->i_mapping->backing_dev_info;
> -
> + return blk_get_backing_dev_info(I_BDEV(inode));
> +#endif
> return sb->s_bdi;
> }
>
> --
> 1.9.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Jan Kara <jack at suse.cz>
SUSE Labs, CR
More information about the linux-mtd
mailing list