diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2024-06-13 20:09:29 +0300 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2024-06-13 20:09:29 +0300 |
| commit | 3572597ca844f625a3c9ba629ed0872b64c16179 (patch) | |
| tree | bed719dc9309aa9734faf1c7776513f007518133 /fs | |
| parent | 2ccbdf43d5e758f8493a95252073cf9078a5fea5 (diff) | |
| parent | 3ac36aa7307363b7247ccb6f6a804e11496b2b36 (diff) | |
| download | linux-3572597ca844f625a3c9ba629ed0872b64c16179.tar.xz | |
Merge tag 'fixes-2024-06-13' of git://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock
Pull memblock fixes from Mike Rapoport:
"Fix validation of NUMA coverage.
memblock_validate_numa_coverage() was checking for a unset node ID
using NUMA_NO_NODE, but x86 used MAX_NUMNODES when no node ID was
specified by buggy firmware.
Update memblock to substitute MAX_NUMNODES with NUMA_NO_NODE in
memblock_set_node() and use NUMA_NO_NODE in x86::numa_init()"
* tag 'fixes-2024-06-13' of git://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock:
x86/mm/numa: Use NUMA_NO_NODE when calling memblock_set_node()
memblock: make memblock_set_node() also warn about use of MAX_NUMNODES
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions