Re: [PATCH] Possible EXT2 File System Corruption in Kernel 2.4

[Andreas Dilger]

On Apr 17, 2002  19:31 +0200, Marc-Christian Petersen wrote:
> your patch does not work:
> 
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.18/include  -Wall -Wstrict-prototypes 
> -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe 
> -mpreferred-stack-boundary=2 -march=i686   -DKBUILD_BASENAME=balloc  -c -o 
> balloc.o balloc.c
> balloc.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.

> balloc.c:397: label `io_error' used but not defined
> balloc.c:383: label `out' used but not defined

??? My patch doesn't touch nor use these labels.

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