From: "Stephen C. Tweedie" <sct@redhat.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Heinz Diehl <hd@cavy.de>, linux-kernel@vger.kernel.org, sct@redhat.com
Subject: Re: [2.5.26] ext3 from Dec. 2001?
Date: Mon, 22 Jul 2002 18:31:32 +0100 [thread overview]
Message-ID: <20020722183132.E10634@redhat.com> (raw)
In-Reply-To: <3D3B8FBE.D5C11685@zip.com.au>; from akpm@zip.com.au on Sun, Jul 21, 2002 at 09:53:18PM -0700
Hi,
On Sun, Jul 21, 2002 at 09:53:18PM -0700, Andrew Morton wrote:
> > Just a short question: is there a patch for 2.5.26 to update ext3 to
> > ext3-0.9.18? There's still ext3-0.9.16 from Dec. 2001 present in 2.5.26.
> > At ../people/sct on ftp.kernel.org there are only updates for kernel
> > 2.2 and 2.4.
>
> 2.5 is uptodate wrt the current ext3-for-2.4 development tree.
> That means that it's more uptodate than 2.4 is...
Yes --- I've been holding back on the changes in the ext3 CVS because
of one nagging bug which I've been hunting for, and which I think I
just found two weeks ago, the day before I left for a holiday. (It's
another possible cause for a "buffer_jdirty()" assert failure in
commit.c on SMP machines.)
I'll get that checked in shortly.
> Some recent changes to ext3 have exposed a data=journal bug
> in 2.5 which is also present in 2.4, but is much harder to hit
> there. I'm not sure what Stephen's intentions are on a 2.4
> upgrade, but I'd be inclined to sit tight until 2.4.20-pre.
I'm just back from holiday so I haven't been able to do much on this
recently, but I've got a fix mostly coded --- it just doesn't
actually work particularly well, yet. :-)
Cheers,
Stephen
prev parent reply other threads:[~2002-07-22 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 15:16 [2.5.26] ext3 from Dec. 2001? Heinz Diehl
2002-07-22 4:53 ` Andrew Morton
2002-07-22 17:31 ` Stephen C. Tweedie [this message]
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=20020722183132.E10634@redhat.com \
--to=sct@redhat.com \
--cc=akpm@zip.com.au \
--cc=hd@cavy.de \
--cc=linux-kernel@vger.kernel.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 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.