From: Nick Piggin <npiggin@suse.de>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: 2.6.29.4: softlockup at find_get_page() et al
Date: Tue, 16 Jun 2009 16:22:14 +0200 [thread overview]
Message-ID: <20090616142214.GB18444@wotan.suse.de> (raw)
In-Reply-To: <20090616131454.GA6168@x200.localdomain>
On Tue, Jun 16, 2009 at 05:14:54PM +0400, Alexey Dobriyan wrote:
> On Tue, Jun 16, 2009 at 03:08:33PM +0200, Nick Piggin wrote:
> > Thanks. Is it rebooted? It would be interesting to know what other
> > CPUs are doing (and even what other tasks are doing) if it is
> > still up.
>
> It was rebooted, sorry.
Thanks. It is hard to know where it is looping, but I see a put_page
in there which seems to suggest it reached at least the "Has the page
moved" test. But if the stack trace is 100% accurate, then it seems
like it has hit the "Has the page been truncated" part of find_lock_page.
And it is an ext2 dir page. And these pages should not get truncated
unless rmdir. But we can't be in rmdir I think because we are doing a
mkdir.
It would seem like the page is still in the pagecache, but ->mapping
is wrong. But actually that is strange because we should have a
new inode here, so find_get_page should not even find a page in
find_or_create_page. There should be no way for a racing thread to
add a page there either.
I would almost have to suspect hardware or software error causing
random memory scribble. I would definitely be very interested if
you can reproduce (I suspect it won't be reproducable though).
Thanks,
Nick
--
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>
parent reply other threads:[~2009-06-16 14:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20090616131454.GA6168@x200.localdomain>]
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=20090616142214.GB18444@wotan.suse.de \
--to=npiggin@suse.de \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox