linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Marc Zyngier <maz@kernel.org>, Mike Rapoport <rppt@kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memblock: restore check for node validity in arch_numa
Date: Fri, 6 Dec 2024 12:26:20 +0200	[thread overview]
Message-ID: <Z1LRTHMT2as5VhEU@kernel.org> (raw)

Hi Linus,

The following changes since commit bcc8eda6d34934d80b96adb8dc4ff5dfc632a53a:

  Merge tag 'turbostat-2024.11.30' of git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux (2024-11-30 18:30:22 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock tags/fixes-2024-12-06

for you to fetch changes up to 180bbad698641873120a48857bb3b9f3166bf684:

  arch_numa: Restore nid checks before registering a memblock with a node (2024-12-01 22:04:52 +0200)

----------------------------------------------------------------
memblock: restore check for node validity in arch_numa

Rework of NUMA initialization in arch_numa dropped a check that refused to
accept configurations with invalid node IDs.

Restore that check to ensure that when firmware passes invalid nodes, such
configuration is rejected and kernel gracefully falls back to dummy NUMA.

----------------------------------------------------------------
Marc Zyngier (1):
      arch_numa: Restore nid checks before registering a memblock with a node

Mike Rapoport (Microsoft) (1):
      memblock: allow zero threshold in validate_numa_converage()

 drivers/base/arch_numa.c | 4 ++++
 mm/memblock.c            | 4 ++--
 2 files changed, 6 insertions(+), 2 deletions(-)

-- 
Sincerely yours,
Mike.


             reply	other threads:[~2024-12-06 10:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 10:26 Mike Rapoport [this message]
2024-12-06 22:01 ` 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=Z1LRTHMT2as5VhEU@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=maz@kernel.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