From: Mel Gorman <mgorman@techsingularity.net>
To: Qian Cai <cai@lca.pw>
Cc: vbabka@suse.cz, Linux-MM <linux-mm@kvack.org>
Subject: Re: low-memory crash with patch "capture a page under direct compaction"
Date: Tue, 5 Mar 2019 14:42:34 +0000 [thread overview]
Message-ID: <20190305144234.GH9565@techsingularity.net> (raw)
In-Reply-To: <604a92ae-cbbb-7c34-f9aa-f7c08925bedf@lca.pw>
On Mon, Mar 04, 2019 at 10:55:04PM -0500, Qian Cai wrote:
> Reverted the patches below from linux-next seems fixed a crash while running LTP
> oom01.
>
> 915c005358c1 mm, compaction: Capture a page under direct compaction -fix
> e492a5711b67 mm, compaction: capture a page under direct compaction
>
> Especially, just removed this chunk along seems fixed the problem.
>
> --- a/mm/compaction.c
> +++ b/mm/compaction.c
> @@ -2227,10 +2227,10 @@ compact_zone(struct compact_control *cc, struct
> capture_control *capc)
> }
>
> /* Stop if a page has been captured */
> - if (capc && capc->page) {
> - ret = COMPACT_SUCCESS;
> - break;
> - }
>
It's hard to make sense of how this is connected to the bug. The
out-of-bounds warning would have required page flags to be corrupted
quite badly or maybe the use of an uninitialised page. How reproducible
has this been for you? I just ran the test 100 times with UBSAN and page
alloc debugging enabled and it completed correctly.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2019-03-05 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 3:55 low-memory crash with patch "capture a page under direct compaction" Qian Cai
2019-03-05 14:42 ` Mel Gorman [this message]
2019-03-05 15:13 ` Qian Cai
2019-03-05 15:27 ` Mel Gorman
2019-03-06 3:01 ` Qian Cai
2019-03-06 3:14 ` Qian Cai
2019-03-06 9:13 ` Mel Gorman
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=20190305144234.GH9565@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=cai@lca.pw \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).