From: Nick Piggin <npiggin@suse.de>
To: mark gross <mgross@linux.intel.com>
Cc: Minchan Kim <minchan.kim@gmail.com>,
linux-mm@kvack.org, Christoph Lameter <cl@linux-foundation.org>
Subject: Re: possible bug in find_get_pages
Date: Tue, 10 Mar 2009 11:45:52 +0100 [thread overview]
Message-ID: <20090310104552.GA4594@wotan.suse.de> (raw)
In-Reply-To: <20090309164316.GB31140@linux.intel.com>
On Mon, Mar 09, 2009 at 09:43:16AM -0700, mark gross wrote:
> On Sat, Mar 07, 2009 at 08:47:32AM +0900, Minchan Kim wrote:
> > Nick already found and solved this problem .
> > It can help you.
> >
> > http://patchwork.kernel.org/patch/860/
> >
>
> Wow, this reads just like the problem we are seeing. I'll try the
> patch and let the test run for a few days!
>
> We've even see it come out of the live lock once in a while as well. I
> was thinking cache coherency HW issue until this :)
>
> I'll send an update after running the test.
Note that after some discussion, the accepted fix looks a bit
different (and might potentially fix another problem if the compiler
gets very smart, although gcc doesn't seem to).
Git commit e8c82c2e23e3527e0c9dc195e432c16784d270fa
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-03-10 10:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 19:26 possible bug in find_get_pages mark gross
2009-03-06 19:28 ` Christoph Lameter
2009-03-06 21:13 ` mark gross
2009-03-06 21:29 ` Christoph Lameter
2009-03-10 10:49 ` Nick Piggin
2009-03-06 23:47 ` Minchan Kim
2009-03-09 16:43 ` mark gross
2009-03-10 10:45 ` Nick Piggin [this message]
2009-03-10 22:49 ` mark gross
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=20090310104552.GA4594@wotan.suse.de \
--to=npiggin@suse.de \
--cc=cl@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mgross@linux.intel.com \
--cc=minchan.kim@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).