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 22:42:32 +0100 [thread overview]
Message-ID: <20100102214232.GA23315@elte.hu> (raw)
In-Reply-To: <20100102203305.GC30016@basil.fritz.box>
* Andi Kleen <andi@firstfloor.org> wrote:
> On Sat, Jan 02, 2010 at 09:11:39PM +0100, Frederic Weisbecker wrote:
> > I've never lost any datas since I began this work. And
> > I run it every day. If I had experienced lock inversions,
> > and sometimes soft lockups, I did not experienced serious
> > damages. It's a journalized filesystem that can fixup the things
> > pretty well.
>
> So are you confident that 2.6.33 will not have regular soft-lockups for
> reiserfs users?
Well, are you confident that your hardware-poison changes in v2.6.33 will not
have any user triggerable bugs? It's a pretty silly question IMO because you
can never be 100% confident.
What matters is for the changes to be sane and clean, for there to be no known
regression and for any reported bugs to be fixed speedily. Which Frederic is
doing in an utmost excellent way ...
Thanks,
Ingo
next prev parent reply other threads:[~2010-01-02 21:42 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 [this message]
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
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=20100102214232.GA23315@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