From: Jane Chu <jane.chu@oracle.com>
To: Matthew Wilcox <willy@infradead.org>, linux-mm@kvack.org
Cc: Miaohe Lin <linmiaohe@huawei.com>,
Naoya Horiguchi <nao.horiguchi@gmail.com>,
Jane Chu <jane.chu@oracle.com>
Subject: Re: madvise_inject_error skips pages
Date: Tue, 16 Jul 2024 14:33:52 -0700 [thread overview]
Message-ID: <9e25253e-7141-493c-9846-dc473284d975@oracle.com> (raw)
In-Reply-To: <ZpaN9-PtftvgTd1s@casper.infradead.org>
Hi, Matthew,
On 7/16/2024 8:12 AM, Matthew Wilcox wrote:
> I was going to send this patch:
>
> +++ b/mm/madvise.c
> @@ -1136,9 +1136,10 @@ static int madvise_inject_error(int behavior,
> /*
> * When soft offlining hugepages, after migrating the page
> * we dissolve it, therefore in the second loop "page" will
> - * no longer be a compound page.
> + * no longer be part of a large folio.
> */
> - size = page_size(compound_head(page));
> + size = folio_size(page_folio(page));
> + start = start & ~(size - 1);
>
> if (behavior == MADV_SOFT_OFFLINE) {
> pr_info("Soft offlining pfn %#lx at process virtual address %#lx\n",
>
> because right now if you start in the middle of (e.g.) an order-4 folio
> followed by an order-0 folio, you'll skip the order-0 folio immediately
> following it.
>
> But then I realised that we can come to this path in the middle of
> a large file-backed folio that's mapped misaligned and has a COW page
> in the middle, and the whole thing is just misguided. So I gave up.
> Anyone want to take a crack at fixing & testing this?
Thanks for the report.
My understanding is, we should run folio_test_large() upfront, and treat
both ends as special case
unless they're folio_size aligned, and iterate in folio_size for the
middle. I think this should work for
hugetlb and large folio in general, but I need to confirm this with tests.
Any thoughts?
BTW, unpoison does look right, I can address them together.
thanks,
-jane
next prev parent reply other threads:[~2024-07-16 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 15:12 Matthew Wilcox
2024-07-16 21:33 ` Jane Chu [this message]
2024-07-17 6:51 ` Miaohe Lin
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=9e25253e-7141-493c-9846-dc473284d975@oracle.com \
--to=jane.chu@oracle.com \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=nao.horiguchi@gmail.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox