From: Daniel Mack <daniel@caiaq.de>
To: TAO HU <tghk48@motorola.com>
Cc: linux-mm@kvack.org, Chang Qing-A21550 <Qing.Chang@motorola.com>,
"Ye Yuan.Bo-A22116" <yuan-bo.ye@motorola.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [Question] race condition in mm/page_alloc.c regarding page->lru?
Date: Fri, 2 Apr 2010 09:06:29 +0200 [thread overview]
Message-ID: <20100402070629.GT30801@buzzloop.caiaq.de> (raw)
In-Reply-To: <g2g5f4a33681004012051wedea9538w9da89e210b731422@mail.gmail.com>
On Fri, Apr 02, 2010 at 11:51:33AM +0800, TAO HU wrote:
> On Thu, Apr 1, 2010 at 12:05 PM, TAO HU <tghk48@motorola.com> wrote:
> > We got a panic on our ARM (OMAP) based HW.
> > Our code is based on 2.6.29 kernel (last commit for mm/page_alloc.c is
> > cc2559bccc72767cb446f79b071d96c30c26439b)
> >
> > It appears to crash while going through pcp->list in
> > buffered_rmqueue() of mm/page_alloc.c after checking vmlinux.
> > "00100100" implies LIST_POISON1 that suggests a race condition between
> > list_add() and list_del() in my personal view.
> > However we not yet figure out locking problem regarding page.lru.
I'm sure this is just a memory corruption which is unrelated to code in
the the memory management area. The code there just happens to trigger
it as it is called frequently and is very sensitive to bogus data
Did you see the other thread I started off yesterday?
http://lkml.indiana.edu/hypermail/linux/kernel/1004.0/00157.html
We could well see the same problem here. Not sure though as any kind of
memory corruption ends up in Ooopses like the ones you see, but it could
be a hint.
Daniel
--
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>
prev parent reply other threads:[~2010-04-02 7:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 4:05 [Question] race condition in mm/page_alloc.c regarding page->lru? TAO HU
2010-04-02 3:51 ` TAO HU
2010-04-02 5:03 ` KOSAKI Motohiro
2010-04-02 5:19 ` TAO HU
2010-04-02 9:48 ` Mel Gorman
2010-04-03 0:59 ` Arve Hjønnevåg
2010-04-04 22:45 ` KOSAKI Motohiro
2010-04-05 10:14 ` Mel Gorman
2010-04-05 10:49 ` Minchan Kim
2010-04-06 3:09 ` [PATCH] mm: Check if any page in a pageblock is reserved before marking it MIGRATE_RESERVE Arve Hjønnevåg
2010-04-06 4:15 ` Minchan Kim
2010-04-06 15:11 ` Mel Gorman
2010-04-02 5:04 ` [Question] race condition in mm/page_alloc.c regarding page->lru? KAMEZAWA Hiroyuki
2010-04-02 5:15 ` Minchan Kim
2010-04-02 7:00 ` TAO HU
2010-04-02 7:22 ` Minchan Kim
2010-04-02 5:13 ` Minchan Kim
2010-04-02 6:48 ` TAO HU
2010-04-02 7:06 ` Daniel Mack [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=20100402070629.GT30801@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=Qing.Chang@motorola.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tghk48@motorola.com \
--cc=yuan-bo.ye@motorola.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).