public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <andi@firstfloor.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Christian Kujau <lists@nerdbynature.de>,
	Alexander Beregalov <a.beregalov@gmail.com>,
	Chris Mason <chris.mason@oracle.com>
Subject: Re: reiserfs broken in 2.6.32 was Re: [GIT PULL] reiserfs fixes
Date: Sat, 2 Jan 2010 21:11:17 +0100	[thread overview]
Message-ID: <20100102201117.GA6971@elte.hu> (raw)
In-Reply-To: <20100102174311.GA30016@basil.fritz.box>


* Andi Kleen <andi@firstfloor.org> wrote:

> > I only have reiserfs partitions in my laptop and my testbox, nothing else. 
> > And that because I'm now maintaining it de facto.
> 
> AFAIK it's widely used in SUSE installations. It was the default for a long 
> time.

[ Btw., if so then SuSE/Novell should sponsor Frederic's reiserfs maintanence 
  work. ]

> And right now as in 2.6.32 it's in a state of "may randomly 
> explode/deadlock". And no clear path out of it. Not good.

You are quite wrong about that accusation: Frederic's changes are not in 
v2.6.32 - they were merged by Linus in the v2.6.33 cycle so that code cannot 
physicaly have caused any problems in v2.6.32 ...

If there's stability problems with reiserfs in v2.6.32 then it's doubly good 
that Linus merged Frederic's tree in v2.6.33 [beyond the obvious advantage 
that it gets rid of the BKL, which was a serious and oft reported limit to 
reiserfs scalability]: finally there's again reiserfs development activity, 
which might lead to further fixes, and which might solve the v2.6.32 stability 
problems you mention.

In my view this work could have been merged sooner, in v2.6.32 already, maybe 
that way the v2.6.32 reiserfs stability problems you mentioned could have been 
avoided.

Thanks,

	Ingo

  parent reply	other threads:[~2010-01-02 20:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-02  1:27 [GIT PULL] reiserfs fixes Frederic Weisbecker
2010-01-02 13:41 ` Andi Kleen
2010-01-02 16:36   ` Frederic Weisbecker
2010-01-02 17:43     ` reiserfs broken in 2.6.32 was " Andi Kleen
2010-01-02 19:02       ` Frederic Weisbecker
2010-01-02 19:23         ` Andi Kleen
2010-01-02 20:11           ` Frederic Weisbecker
2010-01-02 20:33             ` Andi Kleen
2010-01-02 20:54               ` Frederic Weisbecker
2010-01-02 21:10               ` Ingo Molnar
2010-01-02 21:42               ` Ingo Molnar
2010-01-02 21:01             ` tytso
2010-01-02 21:06               ` Frederic Weisbecker
2010-01-02 23:36                 ` tytso
2010-01-02 23:43                   ` Christian Kujau
2010-01-03  1:16                     ` Frederic Weisbecker
2010-01-03  1:52                   ` Frederic Weisbecker
2010-01-03  2:05                     ` Christian Kujau
2010-01-03  3:27                       ` tytso
2010-01-04 20:20                         ` Frederic Weisbecker
2010-01-02 20:11       ` Ingo Molnar [this message]
2010-01-02 22:18       ` Ingo Molnar
2010-01-02 19:19 ` Linus Torvalds
2010-01-02 19:21   ` Linus Torvalds
2010-01-02 19:24     ` Frederic Weisbecker
2010-01-02 19:22   ` Frederic Weisbecker

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=20100102201117.GA6971@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.beregalov@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=chris.mason@oracle.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --cc=torvalds@linux-foundation.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