linux-ext4 - Re: [PATCH] libext2fs: fix i_blocks for extent leaf create/delete

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20120611035301.GA1437@thunk.org>
Date:	Sun, 10 Jun 2012 23:53:01 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Aditya Kali <adityakali@...gle.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [PATCH] libext2fs: fix i_blocks for extent leaf create/delete

On Thu, May 31, 2012 at 11:31:58AM -0700, Aditya Kali wrote:
> When libext2fs allocates/deletes an extent leaf, the i_blocks
> value is incremented/decremented by fs->blocksize / 512. This
> is incorrect in case of bigalloc. The correct way here is to
> use cluster_size / 512.
> The problem is seen if we try to create a large inode using
> libext2fs (say using ext2fs_block_iterate3()) on a bigalloc
> filesystem. fsck catches this and complains.
> 
> Signed-off-by: Aditya Kali <adityakali@...gle.com>

Applied, thanks.

					- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html