All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Denis Vlasenko <vda.linux@googlemail.com>,
	reiser@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: reiser4: maybe just fix bugs?
Date: Tue, 01 Aug 2006 21:52:03 +1000	[thread overview]
Message-ID: <44CF4063.9070003@yahoo.com.au> (raw)
In-Reply-To: <20060801013104.f7557fb1.akpm@osdl.org>

Andrew Morton wrote:
> On Mon, 31 Jul 2006 10:26:55 +0100
> "Denis Vlasenko" <vda.linux@googlemail.com> wrote:
> 
> 
>>The reiser4 thread seem to be longer than usual.
> 
> 
> Meanwhile here's poor old me trying to find another four hours to finish
> reviewing the thing.
> 
> The writeout code is ugly, although that's largely due to a mismatch between
> what reiser4 wants to do and what the VFS/MM expects it to do.  If it
> works, we can live with it, although perhaps the VFS could be made smarter.
> 
> I'd say that resier4's major problem is the lack of xattrs, acls and
> direct-io.  That's likely to significantly limit its vendor uptake.  (As
> might the copyright assignment thing, but is that a kernel.org concern?)
> 
> The plugins appear to be wildly misnamed - they're just an internal
> abstraction layer which permits later feature additions to be added in a
> clean and safe manner.  Certainly not worth all this fuss.
> 
> Could I suggest that further technical critiques of reiser4 include a
> file-and-line reference?  That should ease the load on vger.

I haven't really reviewed it, but when I grepped through it last, I
found a few alarming things, like use of __put_page, trying to remove
pages from pagecache (duplicating parts of vmscan.c, plus bugs), and
taking tree_lock.

Mostly didn't look like big problems to fix, but should be fixed for
mm/ maintainers' sanity. Maybe it's better now, though.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

  parent reply	other threads:[~2006-08-01 11:52 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
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 [this message]
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=44CF4063.9070003@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=vda.linux@googlemail.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 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.