From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Aaron Thompson <dev@aaront.org>, Mike Rapoport <rppt@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memblock: Revert "mm: Always release pages to the buddy allocator in memblock_free_late()."
Date: Sat, 11 Feb 2023 12:13:17 +0200 [thread overview]
Message-ID: <Y+dqPRXSqoP1x7u5@kernel.org> (raw)
Hi Linus,
The following changes since commit 4ec5183ec48656cec489c49f989c508b68b518e3:
Linux 6.2-rc7 (2023-02-05 13:13:28 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock tags/fixes-2023-02-11
for you to fetch changes up to 647037adcad00f2bab8828d3d41cd0553d41f3bd:
Revert "mm: Always release pages to the buddy allocator in memblock_free_late()." (2023-02-07 13:07:37 +0200)
----------------------------------------------------------------
Revert "mm: Always release pages to the buddy allocator in memblock_free_late()."
This reverts commit 115d9d77bb0f9152c60b6e8646369fa7f6167593.
The pages being freed by memblock_free_late() have already been
initialized, but if they are in the deferred init range, __free_one_page()
might access nearby uninitialized pages when trying to coalesce buddies,
which will cause a crash.
A proper fix will be more involved so revert this change for the time
being.
----------------------------------------------------------------
Aaron Thompson (1):
Revert "mm: Always release pages to the buddy allocator in memblock_free_late()."
mm/memblock.c | 8 +-------
tools/testing/memblock/internal.h | 4 ----
2 files changed, 1 insertion(+), 11 deletions(-)
--
Sincerely yours,
Mike.
next reply other threads:[~2023-02-11 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 10:13 Mike Rapoport [this message]
2023-02-11 19:11 ` pr-tracker-bot
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=Y+dqPRXSqoP1x7u5@kernel.org \
--to=rppt@kernel.org \
--cc=dev@aaront.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.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