From: Andreas Dilger <adilger@clusterfs.com>
To: Marc-Christian Petersen <m.c.p@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Possible EXT2 File System Corruption in Kernel 2.4
Date: Wed, 17 Apr 2002 12:33:01 -0600 [thread overview]
Message-ID: <20020417183301.GP20464@turbolinux.com> (raw)
In-Reply-To: <20020417170758.8070026884@smtp.clusterfs.com>
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/
next parent reply other threads:[~2002-04-17 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020417170758.8070026884@smtp.clusterfs.com>
2002-04-17 18:33 ` Andreas Dilger [this message]
2002-04-17 17:31 [PATCH] Possible EXT2 File System Corruption in Kernel 2.4 Marc-Christian Petersen
[not found] <E16vKwg-00056q-00@barry.mail.mindspring.net>
2002-04-11 16:40 ` Frank Krauss
2002-04-17 7:56 ` [PATCH] " Andreas Dilger
2002-05-20 9:38 ` Juan Quintela
2002-05-21 3:57 ` Andreas Dilger
2002-05-21 4:02 ` David S. Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020417183301.GP20464@turbolinux.com \
--to=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox