panics booting NUMA SPARSEMEM on x86_32 NUMA
Status from this message: applied to -tip, thanks Andy.
Get series with b4
b4 am exportbomb.1211277639@pinkyVersions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | x86: reinstate numa remap for SPARSEMEM on x86 NUMA systemsarch/ | +6 | 0 replies | |
| 2/2 | x86: cope with no remap space being allocated for a numa nodearch/ | +1 | 0 replies |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Mel Gorman |
|---|---|
| 1/2 | A-b |
| 2/2 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] panics booting NUMA SPARSEMEM on x86_32 NUMA
We have been seeing panics booting NUMA SPARSEMEM kernels on x86_32 hardware, while trying to allocate node local memory in early boot. These are caused by a miss-allocation of the node pgdat structures when numa remap is disabled.
Following this email are two patches, the first reenables numa remap for SPARSEMEM as the underlying bug has now been fixed. The second hardens the pgdat allocation in the face of there being no numa remap for a particular node (which may still occur).
-apw
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>