From: Luiz Capitulino <luizcap@redhat.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
david@redhat.com, yuzhao@google.com
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org,
muchun.song@linux.dev, lcapitulino@gmail.com, luizcap@redhat.com
Subject: [RFC 0/4] mm: page_ext: Fix crash when reserving 1G pages
Date: Fri, 24 Jan 2025 16:37:50 -0500 [thread overview]
Message-ID: <cover.1737754625.git.luizcap@redhat.com> (raw)
Hi,
[ Thanks to David Hildenbrand for identifying the root cause of this
issue and proving guidance on how to fix it. The new API idea, bugs
and misconceptions are all mine though ]
Currently, trying to reserve 1G pages with page_owner=on and sparsemem
causes a crash. The reproducer is very simple:
1. Build the kernel with CONFIG_SPARSEMEM=y and the table extensions
2. Pass 'default_hugepagesz=1 page_owner=on' in the kernel command-line
3. Reserve one 1G page at run-time, this should crash (see patch 1 for
backtrace)
[ A crash with page_table_check is also possible, but harder to
trigger ]
Apparently, starting with commit e98337d11bbd ("mm/contig_alloc: support
__GFP_COMP") we now pass the full allocation order to page extension
clients and the page extension implementation assumes that all PFNs of
an allocation range will be stored in the same memory section (which is
not true for 1G pages).
To fix this, this series introduces a new iteration API for page extension
objects. The API ensures that we always lookup the memory sections for
the next page extension in the iteration.
While this series seems to fix the issue, it's RFC because:
1. page_ext_iter_next() uses brute-force. David suggested to maintain
the current API but only do a memory section lookup if the next PFN
aligns with PAGE_PER_SECTION (ie. it's the first PFN of a section).
But I couldn't make it work: I was getting random crashes and RCU
warnings
2. It's very lightly tested
Luiz Capitulino (4):
mm: page_ext: add an iteration API for page extensions
mm: page_owner: use new iteration API
mm: page_table_check: use new iteration API
mm: page_ext: drop page_ext_next()
include/linux/page_ext.h | 15 +++++----
mm/page_ext.c | 55 ++++++++++++++++++++++++++++++++
mm/page_owner.c | 68 ++++++++++++++++++++++++++--------------
mm/page_table_check.c | 21 +++++++------
4 files changed, 120 insertions(+), 39 deletions(-)
--
2.47.1
next reply other threads:[~2025-01-24 21:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 21:37 Luiz Capitulino [this message]
2025-01-24 21:37 ` [RFC 1/4] mm: page_ext: add an iteration API for page extensions Luiz Capitulino
2025-02-11 15:25 ` David Hildenbrand
2025-02-11 16:07 ` Luiz Capitulino
2025-01-24 21:37 ` [RFC 2/4] mm: page_owner: use new iteration API Luiz Capitulino
2025-02-11 15:15 ` David Hildenbrand
2025-02-11 16:00 ` Luiz Capitulino
2025-01-24 21:37 ` [RFC 3/4] mm: page_table_check: " Luiz Capitulino
2025-02-11 15:09 ` David Hildenbrand
2025-01-24 21:37 ` [RFC 4/4] mm: page_ext: drop page_ext_next() Luiz Capitulino
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=cover.1737754625.git.luizcap@redhat.com \
--to=luizcap@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=lcapitulino@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=yuzhao@google.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 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.