From: Gregory Maxwell <greg@linuxpower.cx>
To: Brian Wolfe <ahzz@terrabox.com>
Cc: Hans Reiser <reiser@namesys.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Ion Badulescu <ionut@moisil.cs.columbia.edu>,
linux-kernel@vger.kernel.org, reiserfs-list@namesys.com,
Jan Kasprzak <kas@informatics.muni.cz>
Subject: Re: [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related)
Date: Mon, 5 Feb 2001 00:21:19 -0500 [thread overview]
Message-ID: <20010205002119.A31043@xi.linuxpower.cx> (raw)
In-Reply-To: <E14OoD8-0007GI-00@the-village.bc.nu> <3A7B2F7C.52AA6AFA@namesys.com> <20010204205013.D23921@ironsides.terrabox.com>
In-Reply-To: <20010204205013.D23921@ironsides.terrabox.com>; from ahzz@terrabox.com on Sun, Feb 04, 2001 at 08:50:13PM -0600
On Sun, Feb 04, 2001 at 08:50:13PM -0600, Brian Wolfe wrote:
[snip]
> From the debate raging here is what I gathered is acceptable....
>
> make it blow up fataly and immediatly if it detects Red Hat + gcc 2.96-red_hat_broken(forgot version num)
> make it provide a URL to get the patch to remove this safeguard if you really want this.
>
> The fatal crash should be VERY carefull to only trigger on a redhat system with the broken compiler. And to satisfy your agument that people may need to be able to use it, provide a reverse patch to remove this safeguard in one easy cat file | patch.
No. There are *many* other compilers out there which are much *more* broken
then anything RedHat has recently shipped. Unfortunatly, there is no easy
way to accuratly test for such bugs (because once they can be boiled down to
a simple test they are very rapidly fixed, what's left is voodoo).
-
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-05 5:21 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cs.lists.linux-kernel/E14OjME-0006nU-00@the-village.bc.nu>
2001-02-02 21:22 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) Ion Badulescu
2001-02-02 21:57 ` Alan Cox
2001-02-02 22:06 ` Arthur Erhardt
2001-02-02 22:06 ` Hans Reiser
2001-02-02 22:57 ` Ion Badulescu
2001-02-05 2:50 ` Brian Wolfe
2001-02-05 4:08 ` Albert D. Cahalan
2001-02-05 11:58 ` Alan Cox
2001-02-05 11:36 ` Hans Reiser
2001-02-05 12:44 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Alan Cox
2001-02-05 12:16 ` Hans Reiser
2001-02-05 12:52 ` Alan Cox
2001-02-05 12:33 ` Hans Reiser
2001-02-05 12:57 ` Dr. David Gilbert
2001-02-05 16:57 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) James Sutherland
2001-02-12 3:41 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink Albert D. Cahalan
2001-02-12 9:45 ` Hans Reiser
2001-02-05 12:16 ` [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) Dr. David Gilbert
2001-02-05 5:21 ` Gregory Maxwell [this message]
2001-02-05 12:02 ` Alan Cox
2001-02-05 11:38 ` Hans Reiser
2001-02-05 11:55 ` Alan Cox
2001-02-05 11:35 ` Hans Reiser
2001-02-05 20:19 ` Brian Wolfe
2001-02-02 22:42 ` Ion Badulescu
2001-02-03 3:43 ` Johan Kullstam
2001-02-03 8:57 ` [reiserfs-list] " David Ford
2001-02-03 10:00 ` J . A . Magallon
2001-02-03 23:26 ` Felix von Leitner
2001-02-04 11:04 ` Alan Cox
2001-02-04 3:24 ` John Alvord
2001-02-02 11:28 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:15 ` 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=20010205002119.A31043@xi.linuxpower.cx \
--to=greg@linuxpower.cx \
--cc=ahzz@terrabox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ionut@moisil.cs.columbia.edu \
--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