From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: Alexandru Moise <00moses.alexander00@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"khandual@linux.vnet.ibm.com" <khandual@linux.vnet.ibm.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mhocko@suse.com" <mhocko@suse.com>,
"aarcange@redhat.com" <aarcange@redhat.com>,
"minchan@kernel.org" <minchan@kernel.org>,
"hillf.zj@alibaba-inc.com" <hillf.zj@alibaba-inc.com>,
"shli@fb.com" <shli@fb.com>,
"rppt@linux.vnet.ibm.com" <rppt@linux.vnet.ibm.com>,
"kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>,
"mgorman@techsingularity.net" <mgorman@techsingularity.net>,
"rientjes@google.com" <rientjes@google.com>,
"riel@redhat.com" <riel@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] mm, hugetlb, soft_offline: save compound page order before page migration
Date: Wed, 13 Sep 2017 00:13:09 +0000 [thread overview]
Message-ID: <20170913001308.GA13642@hori1.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <20170912204306.GA12053@gmail.com>
Hi Alexandru,
On Tue, Sep 12, 2017 at 10:43:06PM +0200, Alexandru Moise wrote:
> This fixes a bug in madvise() where if you'd try to soft offline a
> hugepage via madvise(), while walking the address range you'd end up,
> using the wrong page offset due to attempting to get the compound
> order of a former but presently not compound page, due to dissolving
> the huge page (since c3114a8).
>
> Signed-off-by: Alexandru Moise <00moses.alexander00@gmail.com>
There was a similar discussion in https://marc.info/?l=linux-kernel&m=150354919510631&w=2
over thp. As I stated there, if we give multi-page range into the parameters
[start, end), we expect that memory errors are injected to every single page
within the range.
So I start to feel that we should revert the following patch which introduced
the multi-page stepping.
commit 20cb6cab52a21b46e3c0dc7bd23f004f810fb421
Author: Wanpeng Li <liwanp@linux.vnet.ibm.com>
Date: Mon Sep 30 13:45:21 2013 -0700
mm/hwpoison: fix traversal of hugetlbfs pages to avoid printk flood
In order to suppress the printk flood, we can use ratelimit mechanism, or
just s/pr_info/pr_debug/ might be ok.
Thanks,
Naoya Horiguchi
> ---
> mm/madvise.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/mm/madvise.c b/mm/madvise.c
> index 21261ff0466f..25bade36e9ca 100644
> --- a/mm/madvise.c
> +++ b/mm/madvise.c
> @@ -625,18 +625,26 @@ static int madvise_inject_error(int behavior,
> {
> struct page *page;
> struct zone *zone;
> + unsigned int order;
>
> if (!capable(CAP_SYS_ADMIN))
> return -EPERM;
>
> - for (; start < end; start += PAGE_SIZE <<
> - compound_order(compound_head(page))) {
> +
> + for (; start < end; start += PAGE_SIZE << order) {
> int ret;
>
> ret = get_user_pages_fast(start, 1, 0, &page);
> if (ret != 1)
> return ret;
>
> + /*
> + * When soft offlining hugepages, after migrating the page
> + * we dissolve it, therefore in the second loop "page" will
> + * no longer be a compound page, and order will be 0.
> + */
> + order = compound_order(compound_head(page));
> +
> if (PageHWPoison(page)) {
> put_page(page);
> continue;
> --
> 2.14.1
>
> --
> 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/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-09-13 0:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 20:43 Alexandru Moise
2017-09-12 20:54 ` Andrew Morton
2017-09-12 20:58 ` Andrew Morton
2017-09-12 21:12 ` Alexandru Moise
2017-09-12 21:10 ` Alexandru Moise
2017-09-13 0:13 ` Naoya Horiguchi [this message]
2017-09-13 8:32 ` Alexandru Moise
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=20170913001308.GA13642@hori1.linux.bs1.fc.nec.co.jp \
--to=n-horiguchi@ah.jp.nec.com \
--cc=00moses.alexander00@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hillf.zj@alibaba-inc.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=shli@fb.com \
/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