> > Applied, thanks. > Shouldn't we finally try to attack "-O ^resize_inode" incompat? The code (ext2fs_create_resize_inode()) for that looks rather ctyptic again, but AFAIKS it deals mostly with checking for badblocks amogst blocks being reserved. Since we do not support badblocks, the code can be simplified...
I attach the relevant portion of code (it is made from original ...create_resize_inode() by iterative throwing away and renaming variables). Can you try to express in terms of algorythm what is done by this code? TIA, -- Vladimir
1.c
Description: Binary data
_______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
