From: Christoph Hellwig <hch@caldera.de>
To: Robert Love <rml@tech9.net>
Cc: Mike Fedyk <mfedyk@matchmail.com>, Ed Tomlinson <tomlins@cam.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] radix-tree pagecache for 2.4.19-pre2-ac2
Date: Mon, 4 Mar 2002 21:35:22 +0100 [thread overview]
Message-ID: <20020304213522.A318@caldera.de> (raw)
In-Reply-To: <20020303210346.A8329@caldera.de> <20020304045557.C1010BA9E@oscar.casa.dyndns.org> <20020304051310.GC1459@matchmail.com> <1015273914.15479.127.camel@phantasy>
In-Reply-To: <1015273914.15479.127.camel@phantasy>; from rml@tech9.net on Mon, Mar 04, 2002 at 03:31:52PM -0500
On Mon, Mar 04, 2002 at 03:31:52PM -0500, Robert Love wrote:
> On Mon, 2002-03-04 at 00:13, Mike Fedyk wrote:
>
> > On Sun, Mar 03, 2002 at 11:55:57PM -0500, Ed Tomlinson wrote:
> >
> > > Got this after a couple of hours with pre2-ac2+preempth+radixtree.
> >
> > Can you try again without preempt?
>
> I've had success with the patch on 2.4.18+preempt and 2.5.5, so I
> suspect preemption is not a problem. I also did not see any
> preempt_schedules in his backtrace ...
I can repdoduce it locally here. IT looks like we leak a pgae with
incorrect flags in an error path. Still investigating it.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@caldera.de>
To: Robert Love <rml@tech9.net>
Cc: Mike Fedyk <mfedyk@matchmail.com>, Ed Tomlinson <tomlins@cam.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] radix-tree pagecache for 2.4.19-pre2-ac2
Date: Mon, 4 Mar 2002 21:35:22 +0100 [thread overview]
Message-ID: <20020304213522.A318@caldera.de> (raw)
In-Reply-To: <1015273914.15479.127.camel@phantasy>; from rml@tech9.net on Mon, Mar 04, 2002 at 03:31:52PM -0500
On Mon, Mar 04, 2002 at 03:31:52PM -0500, Robert Love wrote:
> On Mon, 2002-03-04 at 00:13, Mike Fedyk wrote:
>
> > On Sun, Mar 03, 2002 at 11:55:57PM -0500, Ed Tomlinson wrote:
> >
> > > Got this after a couple of hours with pre2-ac2+preempth+radixtree.
> >
> > Can you try again without preempt?
>
> I've had success with the patch on 2.4.18+preempt and 2.5.5, so I
> suspect preemption is not a problem. I also did not see any
> preempt_schedules in his backtrace ...
I can repdoduce it locally here. IT looks like we leak a pgae with
incorrect flags in an error path. Still investigating it.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-03-04 20:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-03 20:03 [PATCH] radix-tree pagecache for 2.4.19-pre2-ac2 Christoph Hellwig
2002-03-03 20:03 ` Christoph Hellwig
2002-03-04 4:55 ` Ed Tomlinson
2002-03-04 4:55 ` Ed Tomlinson
2002-03-04 5:13 ` Mike Fedyk
2002-03-04 5:13 ` Mike Fedyk
2002-03-04 20:31 ` Robert Love
2002-03-04 20:31 ` Robert Love
2002-03-04 20:35 ` Christoph Hellwig [this message]
2002-03-04 20:35 ` Christoph Hellwig
2002-03-04 5:26 ` Andrew Morton
2002-03-04 5:26 ` Andrew Morton
2002-03-04 20:25 ` Paul P Komkoff Jr
2002-03-04 20:25 ` Paul P Komkoff Jr
2002-03-04 21:04 ` Matt Reppert
2002-03-04 21:04 ` Matt Reppert
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=20020304213522.A318@caldera.de \
--to=hch@caldera.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mfedyk@matchmail.com \
--cc=rml@tech9.net \
--cc=tomlins@cam.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.