From: Chris Mason <mason@suse.com>
To: zole@jblinux.net, linux-kernel@vger.kernel.org
Subject: Re: 2.4.2-acX and reiserfs
Date: Thu, 08 Mar 2001 10:33:40 -0500 [thread overview]
Message-ID: <475580000.984065620@tiny> (raw)
In-Reply-To: <61183.213.142.77.204.984044211.squirrel@diamond.no>
On Thursday, March 08, 2001 08:36:51 AM -0100 "zole@jblinux.net"
<zole@jblinux.net> wrote:
>
> I'm 99.9% certain that those patches referred to have been merged with the
> latest 2.4.2-acX, but just to make it 100% certain I'm asking this
> question. At www.namesys.com, the reiserfs website, I read:
> "Latest patch for linux-2.4.2 contains fixes for tail conversion bug,
> preallocated block leakage, object id sharing problem, dir fsync bug and
> other minor fixes/improvements."
> Have _all_ those fixes gone into the latest ac-patch? (I saw references to
> "tail conversion fixes" and "dir fsync bug" in Alan's Changelog, but I
> didn't find all of them so I'm not sure. :-)
> The reason of why I'm wondering is that I've been having serious trouble
> with reiserfs, and when I'm going for a new fresh installation I want to
> be 100% sure that all fixes have been merged.
> So I would really appreciate a confirmation that all fixes have been
> merged, so I won't have to worry. :-)
Alan has been really proactive at taking the critical bug fixes. He has
all the tail conversion fixes and the dir fsync bug (as does linus). So,
if you are having huge problems with reiserfs on the latest ac series,
please let us know.
The big reiserfs patch that was posted last week wasn't as clean as it
could have been, it has been broken up into smaller units, and the less
important stuff removed. They'll probably post it again this week.
-chris
prev parent reply other threads:[~2001-03-08 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 9:36 2.4.2-acX and reiserfs zole
2001-03-08 15:33 ` Chris Mason [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=475580000.984065620@tiny \
--to=mason@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zole@jblinux.net \
/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