From: Sami Liedes <sami.liedes@iki.fi>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 43227] New: BUG: Bad page state in process wcg_gfam_6.11_i
Date: Fri, 11 May 2012 23:02:13 +0300 [thread overview]
Message-ID: <20120511200213.GB7387@sli.dy.fi> (raw)
In-Reply-To: <20120511125921.a888e12c.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
On Fri, May 11, 2012 at 12:59:21PM -0700, Andrew Morton wrote:
> > [67031.755786] BUG: Bad page state in process wcg_gfam_6.11_i pfn:02519
> > [67031.755790] page:ffffea0000094640 count:0 mapcount:0 mapping:
> > (null) index:0x7f1eb293b
> > [67031.755792] page flags: 0x4000000000000014(referenced|dirty)
>
> AFAICT we got this warning because the page allocator found a free page
> with PG_referenced and PG_dirty set.
>
> It would be a heck of a lot more useful if we'd been told about this
> when the page was freed, not when it was reused! Can anyone think of a
> reason why PAGE_FLAGS_CHECK_AT_FREE doesn't include these flags (at
> least)?
Would it be useful if I tried to reproduce this with some debugging
options turned on, for example CONFIG_DEBUG_VM?
Sami
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-11 20:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-43227-27@https.bugzilla.kernel.org/>
2012-05-11 19:59 ` Andrew Morton
2012-05-11 20:02 ` Sami Liedes [this message]
2012-05-11 20:32 ` Andrew Morton
2012-05-11 20:59 ` Dave Jones
2012-05-11 22:23 ` Sami Liedes
2012-05-14 0:25 ` Dave Jones
2012-05-11 20:06 ` Dave Jones
2012-05-11 20:10 ` Andrew Morton
2012-05-11 22:14 ` Sami Liedes
2012-05-11 21:30 ` Hugh Dickins
2012-05-11 22:56 ` Sami Liedes
2012-05-14 0:30 ` Dave Jones
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=20120511200213.GB7387@sli.dy.fi \
--to=sami.liedes@iki.fi \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.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