linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: Peter Xu <peterx@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	 Andrew Morton <akpm@linux-foundation.org>,
	Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH] mm/page_table_check: Fix crash on ZONE_DEVICE
Date: Wed, 5 Jun 2024 20:01:05 -0400	[thread overview]
Message-ID: <CA+CK2bCCeamiaoTFybTd5nW39ixVPDM2gV2rMmK+2PfFAyE+9w@mail.gmail.com> (raw)
In-Reply-To: <20240605212146.994486-1-peterx@redhat.com>

On Wed, Jun 5, 2024 at 5:21 PM Peter Xu <peterx@redhat.com> wrote:
>
> Not all pages may apply to pgtable check.  One example is ZONE_DEVICE
> pages: they map PFNs directly, and they don't allocate page_ext at all even
> if there's struct page around.  One may reference devm_memremap_pages().
>
> When both ZONE_DEVICE and page-table-check enabled, then try to map some
> dax memories, one can trigger kernel bug constantly now when the kernel was
> trying to inject some pfn maps on the dax device:
>
>  kernel BUG at mm/page_table_check.c:55!
>
> While it's pretty legal to use set_pxx_at() for ZONE_DEVICE pages for page
> fault resolutions, skip all the checks if page_ext doesn't even exist in
> pgtable checker, which applies to ZONE_DEVICE but maybe more.

Thank you for reporting this bug. A few comments below:

>
> Cc: Dan Williams <dan.j.williams@intel.com>
> Cc: Pasha Tatashin <pasha.tatashin@soleen.com>
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
>  mm/page_table_check.c | 11 ++++++++++-
>  1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/mm/page_table_check.c b/mm/page_table_check.c
> index 4169576bed72..509c6ef8de40 100644
> --- a/mm/page_table_check.c
> +++ b/mm/page_table_check.c
> @@ -73,6 +73,9 @@ static void page_table_check_clear(unsigned long pfn, unsigned long pgcnt)
>         page = pfn_to_page(pfn);
>         page_ext = page_ext_get(page);
>
> +       if (!page_ext)
> +               return;

I would replace the above with the following, here and in other places:

if (!page_ext) {
  WARN_ONCE(!is_zone_device_page(page),
                          "page_ext is missing for a non-device page\n");
  return;
}

> +
>         BUG_ON(PageSlab(page));
>         anon = PageAnon(page);
>
> @@ -110,6 +113,9 @@ static void page_table_check_set(unsigned long pfn, unsigned long pgcnt,
>         page = pfn_to_page(pfn);
>         page_ext = page_ext_get(page);
>
> +       if (!page_ext)
> +               return;
> +
>         BUG_ON(PageSlab(page));
>         anon = PageAnon(page);
>
> @@ -140,7 +146,10 @@ void __page_table_check_zero(struct page *page, unsigned int order)
>         BUG_ON(PageSlab(page));
>
>         page_ext = page_ext_get(page);
> -       BUG_ON(!page_ext);
> +
> +       if (!page_ext)
> +               return;
> +
>         for (i = 0; i < (1ul << order); i++) {
>                 struct page_table_check *ptc = get_page_table_check(page_ext);
>
> --
> 2.45.0
>


  parent reply	other threads:[~2024-06-06  0:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 21:21 Peter Xu
2024-06-05 22:05 ` Andrew Morton
2024-06-06 13:14   ` Peter Xu
2024-06-05 22:54 ` Dan Williams
2024-06-05 22:58   ` Alistair Popple
2024-06-06  0:01 ` Pasha Tatashin [this message]
2024-06-06  0:20   ` Dan Williams
2024-06-06  0:24     ` Pasha Tatashin

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=CA+CK2bCCeamiaoTFybTd5nW39ixVPDM2gV2rMmK+2PfFAyE+9w@mail.gmail.com \
    --to=pasha.tatashin@soleen.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=peterx@redhat.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