Hi all.
Druing reading the source codes of indirect index, there is a doubt
in my mind. When using indirect index, physical block number must not
exceed 0x, but I cann' t find any clue about how
ext4_alloc_blocks insure that. Codes that check 64bit_feature is only
in ext4_fill_super and
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 ar
sorry, I mean the fourth parameter of "ext4_ext_put_in_cache.
2007/7/26, Yan Zheng <[EMAIL PROTECTED]>:
Hi all
The third parameter of "ext4_ext_put_in_cache" is used to receive
physical block number. I think the data type should be "ext4_fsblk_t".
Thanks in
Hi all
The third parameter of "ext4_ext_put_in_cache" is used to receive
physical block number. I think the data type should be "ext4_fsblk_t".
Thanks in advance.
YZ
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to [EMAIL PROTECTED]
More major
Hi all
max_debt is used in ext2's find_group_orlov . In ext4's
find_group_orlov, max_debt is only computed, but not used. I wonder
whether it's a typo, Can anyone give me a answer? The kernel source I
read is 2.6.22.
Thanks in advance.
Best Regards
YZ
-
To unsubscribe from