linux-ext4 - [BUG?] "ext4_ext_put_in_cache" uses __u32 to receive physical block number.

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-next>] [day] [month] [year] [list]

Message-ID: <3d0408630707262216i3f8e1c35ub49be9c210f963d8@mail.gmail.com>
Date:	Fri, 27 Jul 2007 13:16:14 +0800
From:	"Yan Zheng" <yanzheng@...n.com>
To:	linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: [BUG?] "ext4_ext_put_in_cache" uses __u32 to receive physical block number.

Hi, all

I think I found a bug in ext4/extents.c, "ext4_ext_put_in_cache" uses
"__u32" to receive physical block number.  "ext4_ext_put_in_cache" is
used in "ext4_ext_get_blocks", it sets ext4 inode's extent cache
according most recently tree lookup (higher 16 bits of saved physical
block number are always zero). when serving a mapping request,
"ext4_ext_get_blocks" first check whether the logical block is in
inode's extent cache. if the logical block is in the cache and the
cached region isn't a gap, "ext4_ext_get_blocks" gets physical block
number by using cached region's physical block number and offset in
the cached region.  as described above, "ext4_ext_get_blocks" may
return wrong result when there are physical block numbers bigger than
0xffffffff.

Regards

YZ
-
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