linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: Vlastimil Babka <vbabka@suse.cz>, Li Wang <liwang@redhat.com>,
	Minchan Kim <minchan@kernel.org>, linux-mm <linux-mm@kvack.org>
Subject: Re: v5.1-rc5 s390x WARNING
Date: Thu, 18 Apr 2019 07:37:12 -0700	[thread overview]
Message-ID: <20190418143711.GF7751@bombadil.infradead.org> (raw)
In-Reply-To: <20190418135452.GF18914@techsingularity.net>

On Thu, Apr 18, 2019 at 02:54:52PM +0100, Mel Gorman wrote:
> > > [ 1422.124060] WARNING: CPU: 0 PID: 9783 at mm/page_alloc.c:3777 __alloc_pages_irect_compact+0x182/0x190

We lost a character here?  "_irect_" should surely be "_direct_"

> ---8<---
> mm, page_alloc: Always use a captured page regardless of compaction result
> 
> During the development of commit 5e1f0f098b46 ("mm, compaction: capture
> a page under direct compaction"), a paranoid check was added to ensure
> that if a captured page was available after compaction that it was
> consistent with the final state of compaction. The intent was to catch
> serious programming bugs such as using a stale page pointer and causing
> corruption problems.
> 
> However, it is possible to get a captured page even if compaction was
> unsuccessful if an interrupt triggered and happened to free pages in
> interrupt context that got merged into a suitable high-order page. It's
> highly unlikely but Li Wang did report the following warning on s390
> 
> [ 1422.124060] WARNING: CPU: 0 PID: 9783 at mm/page_alloc.c:3777 __alloc_pages_irect_compact+0x182/0x190

... so it probably needs to be corrected here.


  reply	other threads:[~2019-04-18 14:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17  8:35 Li Wang
2019-04-17  8:54 ` Vlastimil Babka
2019-04-18 13:54   ` Mel Gorman
2019-04-18 14:37     ` Matthew Wilcox [this message]
2019-04-18 15:25       ` Mel Gorman
2019-04-19 12:53         ` Vlastimil Babka
2019-04-19  8:41     ` Li Wang
2019-04-19  8:52       ` Mel Gorman
2019-04-19 12:51     ` Vlastimil Babka

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=20190418143711.GF7751@bombadil.infradead.org \
    --to=willy@infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=liwang@redhat.com \
    --cc=mgorman@techsingularity.net \
    --cc=minchan@kernel.org \
    --cc=vbabka@suse.cz \
    /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