public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Ricky Beam <jfbeam@bluetronic.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.70
Date: Wed, 28 May 2003 01:15:46 +0400	[thread overview]
Message-ID: <3ED3D582.4080303@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0305271048380.6665-100000@penguin.transmeta.com>

Linus Torvalds wrote:

>
>This is not just a core kernel issue - we've seen this with subsystems 
>like ext3 and ReiserFS: they were "finished' and "stable", but what made 
>them _really_ stable was a release or two on vendor kernels, and thousands 
>of users.
>
>  
>
I wish this wasn't true, but it was.  When I say something is stable, I 
mean that we have fixed every reported bug.

I have this hypothesis of software engineering which is that every order 
of magnitude increase in the number of users finds as many bugs as the 
previous order of magnitude increase.

With ReiserFS, I several times publicly said that it was stable, and for 
that order of magnitude of users it was, and then the order of magnitude 
changed and it wasn't....

With V4 we are going to benefit from an accumulation of testing scripts 
(and more experience at what we do plus less hurried code), and that 
will put us a few orders of magnitude farther ahead.

It will be a bit ironic that V4 is architected for greater data security 
with its atomic filesystem operations, and yet V3 will for quite some 
time offer greater data security in reality.

(V4 is currently being tuned for CPU consumption, and its VM 
interaction.  We have some fond hope of releasing in July.)

-- 
Hans



  reply	other threads:[~2003-05-27 21:03 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-27  2:08 Linux 2.5.70 Linus Torvalds
2003-05-27  2:45 ` Linux 2.5.70 (Compiler warnings) Udo A. Steinberg
2003-05-27  3:09   ` YOSHIFUJI Hideaki / 吉藤英明
2003-05-27  7:10     ` David S. Miller
2003-05-27  8:48 ` Linux 2.5.70 compile error DevilKin
2003-05-27 13:05   ` William Lee Irwin III
2003-05-27 15:29     ` DevilKin-LKML
2003-05-27 15:36       ` William Lee Irwin III
2003-05-27 15:48         ` John Stoffel
2003-05-27 15:52           ` William Lee Irwin III
2003-05-27 16:35             ` John Stoffel
2003-05-27 16:43               ` William Lee Irwin III
2003-05-27 17:50                 ` John Stoffel
2003-05-27 17:56                   ` William Lee Irwin III
2003-05-27 21:56                   ` Martin J. Bligh
2003-05-27 18:19           ` Roman Zippel
2003-05-27 18:40             ` Dave Jones
2003-05-27 18:50               ` William Lee Irwin III
2003-05-27 21:59               ` Martin J. Bligh
2003-05-27 23:40                 ` Dave Jones
2003-05-28  3:20                   ` Martin J. Bligh
2003-05-28  3:34                 ` William Lee Irwin III
2003-05-28  6:11                   ` Martin J. Bligh
2003-05-28  7:43                     ` William Lee Irwin III
2003-05-28 15:28                       ` Martin J. Bligh
2003-05-29  1:14                         ` William Lee Irwin III
2003-05-28  6:52                   ` Dave Jones
2003-05-28 22:08                 ` Bill Davidsen
2003-05-29  0:36                   ` Martin J. Bligh
2003-05-27 19:46             ` John Stoffel
2003-05-27 15:38       ` Sean Neakums
2003-05-27 15:52         ` Martin J. Bligh
2003-05-27 16:58 ` Linux 2.5.70 Ricky Beam
2003-05-27 17:26   ` Linus Torvalds
2003-05-27 16:48     ` Alan Cox
2003-05-27 17:53       ` Linus Torvalds
2003-05-27 21:15         ` Hans Reiser [this message]
2003-05-27 18:09     ` Ricky Beam
2003-05-27 18:22       ` Jeff Garzik
2003-05-27 18:31       ` Robert Love
2003-05-27 19:18       ` Adrian Bunk
2003-05-28 16:08       ` Bill Davidsen
2003-05-28 15:58     ` Bill Davidsen
2003-05-28 16:14       ` Linus Torvalds
2003-05-28 19:22         ` ismail (cartman) donmez
2003-05-29 11:14           ` Dave Jones
2003-05-29 11:14             ` ismail (cartman) donmez
2003-05-28 22:40         ` Bill Davidsen
2003-05-27 21:06   ` Andreas Boman
2003-05-28  2:30   ` Daniel Phillips
2003-05-27 21:42 ` John Cherry
2003-05-28 17:55   ` John Cherry
2003-05-28  5:45 ` [PATCH] register_ioctl32_conversion symbol exports fix Andres Salomon
     [not found]   ` <20030528074701.GA17449@fs.tum.de>
2003-05-28  8:05     ` Andres Salomon
2003-05-28 14:59 ` Linux 2.5.70 Paweł Gołaszewski
  -- strict thread matches above, loose matches on Subject: below --
2003-05-27  5:13 Louis Garcia
     [not found] <200305271012.h4RACbE04869@quatramaran.ens.fr>
2003-05-27 10:15 ` Éric Brunet
     [not found] <mailman.1054055041.7585.linux-kernel2news@redhat.com>
2003-05-27 21:25 ` Pete Zaitcev
2003-05-28 15:08 Petr Vandrovec
2003-05-28 15:56 ` Paweł Gołaszewski

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=3ED3D582.4080303@namesys.com \
    --to=reiser@namesys.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jfbeam@bluetronic.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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