From: Marc-Christian Petersen <mcp@linux-systeme.de>
To: Daniel Phillips <phillips@arcor.de>,
Andreas Dilger <adilger@clusterfs.com>
Cc: Daniel Phillips <phillips@bonn-fries.net>, linux-kernel@vger.kernel.org
Subject: Re: htree directory indexing 2.4.18-2 BUG with highmem and also high i/o
Date: Thu, 11 Jul 2002 01:03:37 +0200 [thread overview]
Message-ID: <200207110103.37380.mcp@linux-systeme.de> (raw)
In-Reply-To: <E17SQE4-00029R-00@starship>
On Thursday 11 July 2002 00:46, Daniel Phillips wrote:
Hi Daniel, Hi Andreas,
> On Wednesday 10 July 2002 23:01, Andreas Dilger wrote:
> > On Jul 09, 2002 23:33 +0200, Marc-Christian Petersen wrote:
> > > Hi Daniel,
> > >
> > > I've found a bug with htree directory indexing patch and
> > > highmem enabled (64GB). This is with 2.4.18 and htree patch
> > > 2.4.18-2. Oops appears if accessing an ext2 partition with ls
> > > or doing "who/w" in the directory of the ext2 partition.
> >
> > The ext2 htree patch probably needs to add a "kmap()" and "kunmap()"
> > in the function that reads a page and scans the directory for the
> > name it is looking for. I can't be any more specific than this
> > right now since I only have the ext3 version of this patch, and it
> > does not have page-cache based directories (it is still using the
> > buffer cache).
Say, where can i find those patch for ext3? I've searched a long time and
never found it?! :|
--
Kind regards
Marc-Christian Petersen
http://sourceforge.net/projects/wolk
PGP/GnuPG Key: 1024D/408B2D54947750EC
Fingerprint: 8602 69E0 A9C2 A509 8661 2B0B 408B 2D54 9477 50EC
Key available at www.keyserver.net. Encrypted e-mail preferred.
next prev parent reply other threads:[~2002-07-10 23:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 21:33 htree directory indexing 2.4.18-2 BUG with highmem and also high i/o Marc-Christian Petersen
2002-07-10 21:01 ` Andreas Dilger
2002-07-10 22:46 ` Daniel Phillips
2002-07-10 23:03 ` Marc-Christian Petersen [this message]
2002-07-11 0:49 ` Andreas Dilger
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=200207110103.37380.mcp@linux-systeme.de \
--to=mcp@linux-systeme.de \
--cc=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@arcor.de \
--cc=phillips@bonn-fries.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 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.