From: Denis Vlasenko <vda.linux@googlemail.com>
To: "Horst H. von Brand" <vonbrand@inf.utfsm.cl>, reiser@namesys.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: reiser4: maybe just fix bugs?
Date: Mon, 31 Jul 2006 22:06:42 +0200 [thread overview]
Message-ID: <200607312206.42240.vda.linux@googlemail.com> (raw)
In-Reply-To: <200607311617.k6VGH3YH009055@laptop13.inf.utfsm.cl>
On Monday 31 July 2006 18:17, Horst H. von Brand wrote:
> > Not too bad when compared to other FSes, but still.
>
> How did you compare?
Because as I can see on lkml, other FSes also have deadlock-on-oom
bugs. Linus also talked about ext3 inodes being insanely big.
> > When singled out, none of these things are bad enough to hold off
> > inclusion. However, combined impact of _both_ of them
> > did upset maintainers enough.
>
> Plus a, lets say, less than cooperative overall attitude, and a marked
> tendency to try to sneak changes in by political arm-twisting.
Yes, this is present to a degree.
> > Frankly, on the first problem I think that you are right, Hans, and
> > putting plugins into VFS _now_ makes little sense because we can't know
> > whether anybody will ever want to have plugins for some other FS, so
> > requiring reiser people to do all the shuffling _now_ for questionable
> > gain is simply not fair. It can be done later if needed.
>
> You are wrong. ReiserFS has no "right" to be allowed into the kernel.
JBD is factored out. So far it was a wasted effort - nobody uses
JBD except ext3.
--
vda
next prev parent reply other threads:[~2006-07-31 20:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 9:26 reiser4: maybe just fix bugs? Denis Vlasenko
2006-07-31 12:38 ` Adrian Bunk
2006-07-31 16:17 ` Horst H. von Brand
2006-07-31 20:06 ` Denis Vlasenko [this message]
2006-08-01 15:22 ` Theodore Tso
2006-08-01 2:30 ` Hans Reiser
2006-08-01 10:37 ` Pavel Machek
2006-08-01 13:59 ` Scott J. Harmon
2006-08-02 6:22 ` Jan Engelhardt
2006-08-02 19:53 ` Denis Vlasenko
2006-08-01 8:31 ` Andrew Morton
2006-08-01 2:18 ` Hans Reiser
2006-08-01 11:24 ` Vladimir V. Saveliev
2006-08-01 14:33 ` Andrew Morton
2006-08-01 15:07 ` Vladimir V. Saveliev
2006-08-01 16:55 ` David Masover
2006-08-01 19:26 ` Nate Diller
2006-08-02 3:54 ` David Masover
2006-08-03 7:46 ` Theodore Tso
2006-08-04 21:09 ` David Masover
2006-08-01 19:14 ` Nate Diller
2006-08-01 11:43 ` Christoph Hellwig
2006-08-01 11:52 ` Nick Piggin
2006-08-01 14:54 ` Andrew Morton
2006-08-01 19:32 ` Andi Kleen
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=200607312206.42240.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=vonbrand@inf.utfsm.cl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.