From: Francesco Dolcini <francesco.dolcini@toradex.com>
To: Dong Aisheng <dongas86@gmail.com>,
Chen Wandun <chenwandun@huawei.com>,
akpm@linux-foundation.org, guillaume.tucker@collabora.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "mm/page_isolation: unset migratetype directly for non Buddy page"
Date: Mon, 24 Jan 2022 09:41:51 +0100 [thread overview]
Message-ID: <20220124084151.GA95197@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <CAA+hA=Rg=uRb_sVvSr4P=rbfbp5MTBmkGJ4pdsd-6wMRPeK39g@mail.gmail.com>
On Tue, Jan 18, 2022 at 09:50:42PM +0800, Dong Aisheng wrote:
> On Mon, Jan 17, 2022 at 10:12 PM Chen Wandun <chenwandun@huawei.com> wrote:
> >
> > This reverts commit 075782149abff45ee22f27315eced44d02b96779.
> >
> > commit 075782149abf ("mm/page_isolation: unset migratetype directly for
> > non Buddy page") will result memory that should in buddy disappear by
> > mistake. move_freepages_block move all pages in pageblock instead of
> > pages indicated by input parameter, so if input pages is not in buddy
> > but other pages in pageblock is in buddy, it will result in page out of
> > control.
> >
> > Reported-by: "kernelci.org bot" <bot@kernelci.org>
> > Signed-off-by: Chen Wandun <chenwandun@huawei.com>
>
> The original patch broke imx6ul evk booting up.
> Tested-by: Dong Aisheng <aisheng.dong@nxp.com>
Same issue present on imx7.
Tested-by: Francesco Dolcini <francesco.dolcini@toradex.com>
next prev parent reply other threads:[~2022-01-24 8:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 14:27 [PATCH] Revert "mm/page_isolation: unset migratetype directly for non Buddy page" Chen Wandun
2022-01-17 15:32 ` David Hildenbrand
2022-01-26 2:17 ` Chen Wandun
2022-01-18 13:50 ` Dong Aisheng
2022-01-24 8:41 ` Francesco Dolcini [this message]
2022-01-25 16:40 ` Vlastimil Babka
2022-01-26 2:18 ` Chen Wandun
2022-01-30 9:24 ` Thorsten Leemhuis
2022-01-31 22:39 ` Andrew Morton
2022-02-05 5:15 ` Thorsten Leemhuis
2022-01-26 21:11 ` Guenter Roeck
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=20220124084151.GA95197@francesco-nb.int.toradex.com \
--to=francesco.dolcini@toradex.com \
--cc=akpm@linux-foundation.org \
--cc=chenwandun@huawei.com \
--cc=dongas86@gmail.com \
--cc=guillaume.tucker@collabora.com \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.