lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 11 Oct 2012 19:54:08 +0200
From:	Jan Kara <jack@...e.cz>
To:	Namjae Jeon <linkinjeon@...il.com>
Cc:	jack@...e.cz, linux-kernel@...r.kernel.org,
	Namjae Jeon <namjae.jeon@...sung.com>,
	Ashish Sangwan <a.sangwan@...sung.com>
Subject: Re: [PATCH 3/6] udf: update inode's iblock count when allocating
 new block

On Wed 10-10-12 00:09:28, Namjae Jeon wrote:
> From: Namjae Jeon <namjae.jeon@...sung.com>
> 
> 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@...sung.com>
> Signed-off-by: Ashish Sangwan <a.sangwan@...sung.com>
> ---
>  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@...e.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ