linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sami Liedes <sami.liedes@iki.fi>,
	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 16:59:13 -0400	[thread overview]
Message-ID: <20120511205913.GA15539@redhat.com> (raw)
In-Reply-To: <20120511133234.6130b69a.akpm@linux-foundation.org>

On Fri, May 11, 2012 at 01:32:34PM -0700, Andrew Morton wrote:
 > On Fri, 11 May 2012 23:02:13 +0300
 > Sami Liedes <sami.liedes@iki.fi> wrote:
 > 
 > > 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?
 > > 
 > 
 > Sure, thanks, that might turn something up. 
 > Documentation/SubmitChecklist recommends 
 > 
 > : 12: Has been tested with CONFIG_PREEMPT, CONFIG_DEBUG_PREEMPT,
 > :     CONFIG_DEBUG_SLAB, CONFIG_DEBUG_PAGEALLOC, CONFIG_DEBUG_MUTEXES,
 > :     CONFIG_DEBUG_SPINLOCK, CONFIG_DEBUG_ATOMIC_SLEEP, CONFIG_PROVE_RCU
 > :     and CONFIG_DEBUG_OBJECTS_RCU_HEAD all simultaneously enabled.
 > 
 > although that list might be a bit out of date; it certainly should
 > include CONFIG_DEBUG_VM!

FWIW, that Fedora report of this had DEBUG_VM enabled, and it doesn't
seem that there was any earlier oops/warn judging by the lack of tainting.

	Dave

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2012-05-11 20:59 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 ` [Bug 43227] New: BUG: Bad page state in process wcg_gfam_6.11_i Andrew Morton
2012-05-11 20:02   ` Sami Liedes
2012-05-11 20:32     ` Andrew Morton
2012-05-11 20:59       ` Dave Jones [this message]
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=20120511205913.GA15539@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sami.liedes@iki.fi \
    /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).