Re: [PATCH 3/6] udf: update inode's iblock count when allocatingnew block

[Jan Kara]

On Wed 10-10-12 00:09:28, Namjae Jeon wrote:
> From: Namjae Jeon <namjae.jeon@xxxxxxxxxxx>
> 
> Currently, du will show wrong block count. This patch fix it.
  This should be fixed by commit fd4287dbc07763595c1e74edbb6520092290185c.
Have you tested with newish kernel? If recent kernel still has an issue,
can you provide a test case? Thanks!

								Honza

> 
> Signed-off-by: Namjae Jeon <namjae.jeon@xxxxxxxxxxx>
> Signed-off-by: Ashish Sangwan <a.sangwan@xxxxxxxxxxx>
> ---
>  fs/udf/inode.c |    2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/fs/udf/inode.c b/fs/udf/inode.c
> index 8266f2e..76a1f57 100644
> --- a/fs/udf/inode.c
> +++ b/fs/udf/inode.c
> @@ -775,6 +775,8 @@ static sector_t inode_getblk(struct inode *inode, sector_t block,
>  		if (isBeyondEOF)
>  			iinfo->i_lenExtents += inode->i_sb->s_blocksize;
>  	}
> +	/* update inode's iblocks */
> +	inode->i_blocks += (1 << (inode->i_sb->s_blocksize_bits - 9));
>  
>  	/* if the extent the requsted block is located in contains multiple
>  	 * blocks, split the extent into at most three extents. blocks prior
> -- 
> 1.7.9.5
> 
-- 
Jan Kara <jack@xxxxxxx>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/