From: Hans Reiser <reiser@namesys.com>
To: Alan Cox <alan@redhat.com>
Cc: Chris Mason <mason@suse.com>,
Jan Kasprzak <kas@informatics.muni.cz>,
linux-kernel@vger.kernel.org, reiserfs-list@namesys.com,
"Yury Yu. Rupasov" <yura@yura.polnet.botik.ru>
Subject: Re: ReiserFS Oops (2.4.1, deterministic, symlink
Date: Fri, 02 Feb 2001 23:43:38 +0300 [thread overview]
Message-ID: <3A7B1BFA.F7B4EAD@namesys.com> (raw)
In-Reply-To: <200102021825.f12IPCu20705@devserv.devel.redhat.com>
Alan Cox wrote:
>
> > So, did Linus say no? If not, let's ask him with a patch. Quite simply,
> > neither we nor the users should be burdened with this, and the patch removes
> > the burden.
>
> Since egcs-1.1.2 and gcc 2.95 miscompile the kernel strstr code dont forget
> to stop those being used as well. Oh look you'll need CVS gcc to build the
> kernel... ah but wait that misbuilds DAC960.c...
>
> Oh look nothing compiles the kernel.
>
> Congratulations 8)
>
> Alan
Users cannot use gcc 2.96 as shipped in RedHat 7.0 if they want to use
reiserfs. It is that simple. How can you even consider defending allowing the
use of it without requiring a positive affirmation by the user that they don't
know what they are doing and want to do it anyway?:-) I could understand
arguing that you don't want to be bothered with protecting the users because you
don't have the time, but if somebody else finds the time to write the patch....
I would indeed encourage Linus to accept patches to test for known bad compilers
at make time. It is less work for us all to prevent users from having bugs than
to respond to their having them. I look forward to gcc 3.00, and I encourage
the compiler guys to get over being (understandably) irked that somebody else
released their code prematurely, and to increment the version number to 2.97 so
that users can more easily avoid the baddie.
Hans
-
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 21:15 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
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 [this message]
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=3A7B1BFA.F7B4EAD@namesys.com \
--to=reiser@namesys.com \
--cc=alan@redhat.com \
--cc=kas@informatics.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=reiserfs-list@namesys.com \
--cc=yura@yura.polnet.botik.ru \
/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