From: Hans Reiser <reiser@namesys.com>
To: arjanv@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops in reiserfs w/2.4.7-10
Date: Mon, 12 Nov 2001 17:33:31 +0300 [thread overview]
Message-ID: <3BEFDDBB.2090605@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111122233530.26293-100000@bad-sports.com> <3BEFBDE0.6080804@namesys.com> <3BEFC301.A92C64D4@redhat.com>
We have now tested the latest Red Hat 7.2 kernel (2.4.7.-10) and it
passes our regression tests, which means that it is indeed a reasonably
stable kernel that I would be willing to put my home directory on if it
was me and I wasn't using NFS on it. (I used 2.4.5 on my laptop for
months with no problem, and I would guess that it is as stable as that
one, when we talk about stable, remember we mean stable for a a few
hundred thousand users). The latest Linus kernels will be more stable,
and since Linux is still stabilizing, I would guess that using a recent
kernel is going to remain a good idea for the next few months.
Apologies to Red Hat for relying on second hand reports, and for that
reason advising users to go to a kernel I had more knowledge about.
Users using NFS should keep a watch on the recently found bug involving
rename, I think a patch just came out recently, and I expect it will be
going into the kernel soon.
Hans
next prev parent reply other threads:[~2001-11-12 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 11:37 Oops in reiserfs w/2.4.7-10 brett
2001-11-12 12:17 ` Hans Reiser
2001-11-12 12:39 ` Arjan van de Ven
2001-11-12 13:55 ` Hans Reiser
2001-11-12 14:33 ` Hans Reiser [this message]
2001-11-12 15:06 ` Hans Reiser
2001-11-12 12:54 ` Alan Cox
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=3BEFDDBB.2090605@namesys.com \
--to=reiser@namesys.com \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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