From: Chris Mason <mason@suse.com>
To: Alan Cox <alan@redhat.com>, Hans Reiser <reiser@namesys.com>
Cc: Jan Kasprzak <kas@informatics.muni.cz>,
linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: ReiserFS Oops (2.4.1, deterministic, symlink
Date: Fri, 02 Feb 2001 10:16:29 -0500 [thread overview]
Message-ID: <595250000.981126989@tiny> (raw)
In-Reply-To: <E14OfIl-0006P1-00@the-village.bc.nu>
On Friday, February 02, 2001 12:26:52 PM +0000 Alan Cox
<alan@lxorguk.ukuu.org.uk> wrote:
>> This is why our next patch will detect the use of gcc 2.96, and
>> complain, in the reiserfs Makefile.
>
> What makes you think its gcc 2.96 ?
>
We have had many reports of exactly this symlink problem, and each time it
was a redhat user with a gcc 2.96, and switching to kgcc fixed it. We have
one report (now two with Alan's) that 2.96-69 does not show this crash.
Hans, decisions about proper compilers should not be made in each
individual part of the kernel. If unpatched gcc 2.96 is getting reiserfs
wrong, it is compiling other parts of the kernel wrong as well. l-k has
discussed this at length already ;-)
> If the person concerned can clarify what they built with (2.96-69 or
> egcs-1.1.2 (kgcc)), that would be useful.
>
> I've certainly done the Reiserfs testing I did with gcc 2.96-69 with no
> problems at all. Reiserfsck was having _bad_ problems but I saw those with
> egcs-1.1.2 too and I understand there is a new reiserfsck about to appear
> or just out which is much better.
>
Yes.
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-02 15:20 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 11:28 ReiserFS Oops (2.4.1, deterministic, symlink related) Jan Kasprzak
2001-02-02 11:04 ` [reiserfs-list] " Hans Reiser
2001-02-02 12:16 ` Jan Kasprzak
2001-02-02 12:34 ` Alan Cox
2001-02-02 13:09 ` Jan Kasprzak
2001-02-02 16:36 ` Jan Kasprzak
2001-02-02 16:46 ` Alan Cox
2001-02-02 12:26 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Alan Cox
2001-02-02 15:16 ` Chris Mason [this message]
2001-02-02 15:20 ` Alan Cox
2001-02-02 17:34 ` Hans Reiser
2001-02-02 18:25 ` Alan Cox
2001-02-02 20:43 ` Hans Reiser
2001-02-02 21:33 ` Alan Cox
2001-02-02 21:29 ` [reiserfs-list] " Hans Reiser
2001-02-02 22:13 ` Alan Cox
2001-02-02 22:13 ` Hans Reiser
2001-02-02 23:40 ` J . A . Magallon
2001-02-02 23:34 ` Hans Reiser
2001-02-03 0:17 ` Jakub Jelinek
2001-02-03 4:25 ` Paul Jakma
2001-02-03 7:58 ` Alan Cox
2001-02-03 9:18 ` J . A . Magallon
2001-02-03 9:48 ` Jakub Jelinek
2001-02-03 7:46 ` Alan Cox
2001-02-03 17:14 ` David Woodhouse
2001-02-03 17:33 ` Albert D. Cahalan
2001-02-03 17:56 ` Alan Cox
2001-02-03 23:49 ` Albert D. Cahalan
2001-02-02 21:34 ` John Morrison
2001-02-02 21:39 ` Alan Cox
2001-02-02 21:49 ` John Morrison
2001-02-02 22:03 ` Hans Reiser
2001-02-02 22:40 ` Alan Cox
2001-02-02 22:16 ` Hans Reiser
2001-02-02 22:58 ` alex
2001-02-03 0:40 ` Andre Pang
2001-02-03 2:22 ` James Sutherland
2001-02-02 22:52 ` Keith Owens
2001-02-09 9:39 ` Thomas Zehetbauer
2001-02-02 12:15 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) John Morrison
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=595250000.981126989@tiny \
--to=mason@suse.com \
--cc=alan@redhat.com \
--cc=kas@informatics.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
/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