Possible EXT2 File System Corruption in Kernel 2.4
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 8 lines · Marc-Christian Petersen
your patch does not work:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.18/include -Wall -Wstrict-prototypes
(quoted diff) +0
-2-Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -DKBUILD_BASENAME=balloc -c -oballoc.o
balloc.cballoc.c: In function `ext2_new_block':
balloc.c:524: warning: long unsigned int format, unsigned int arg (arg 4)
OK, minor error there - "tmp" is an int in ext2_new_block, while "block" is a long in ext2_free_blocks (I had changed it to a long in my tree and didn't see the warning when it compiled). I should probably submit a patch at some point, but for now 32 bits is enough.
Quoted 2 lines
balloc.c:397: label
io_error' used but not defined balloc.c:383: labelout' used but not defined
??? My patch doesn't touch nor use these labels.
Quoted 1 line
gcc: Internal compiler error: program cc1 got fatal signal 11
??? This is pretty bad - usually signal 11 from GCC means RAM problems.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/