# git rev-parse -q --verify 4aa9fc2a435abe95a1e8d7f8c7b3d6356514b37a^{commit}
4aa9fc2a435abe95a1e8d7f8c7b3d6356514b37a
already have revision, skipping fetch
# git checkout -q -f -B kisskb 4aa9fc2a435abe95a1e8d7f8c7b3d6356514b37a
# git clean -qxdf
# < git log -1
# commit 4aa9fc2a435abe95a1e8d7f8c7b3d6356514b37a
# Author: Michal Hocko <mhocko@suse.com>
# Date:   Fri Jan 25 19:08:58 2019 +0100
# 
#     Revert "mm, memory_hotplug: initialize struct pages for the full memory section"
#     
#     This reverts commit 2830bf6f05fb3e05bc4743274b806c821807a684.
#     
#     The underlying assumption that one sparse section belongs into a single
#     numa node doesn't hold really. Robert Shteynfeld has reported a boot
#     failure. The boot log was not captured but his memory layout is as
#     follows:
#     
#       Early memory node ranges
#         node   1: [mem 0x0000000000001000-0x0000000000090fff]
#         node   1: [mem 0x0000000000100000-0x00000000dbdf8fff]
#         node   1: [mem 0x0000000100000000-0x0000001423ffffff]
#         node   0: [mem 0x0000001424000000-0x0000002023ffffff]
#     
#     This means that node0 starts in the middle of a memory section which is
#     also in node1.  memmap_init_zone tries to initialize padding of a
#     section even when it is outside of the given pfn range because there are
#     code paths (e.g.  memory hotplug) which assume that the full worth of
#     memory section is always initialized.
#     
#     In this particular case, though, such a range is already intialized and
#     most likely already managed by the page allocator.  Scribbling over
#     those pages corrupts the internal state and likely blows up when any of
#     those pages gets used.
#     
#     Reported-by: Robert Shteynfeld <robert.shteynfeld@gmail.com>
#     Fixes: 2830bf6f05fb ("mm, memory_hotplug: initialize struct pages for the full memory section")
#     Cc: stable@kernel.org
#     Signed-off-by: Michal Hocko <mhocko@suse.com>
#     Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
# < /opt/cross/kisskb/gcc-4.6.3-nolibc/mips-linux/bin/mips-linux-gcc --version
# < /opt/cross/kisskb/gcc-4.6.3-nolibc/mips-linux/bin/mips-linux-ld --version
# < git log --format=%s --max-count=1 4aa9fc2a435abe95a1e8d7f8c7b3d6356514b37a
# < make -s -j 48 ARCH=mips O=/kisskb/build/linus_mips-allnoconfig_mips CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/mips-linux/bin/mips-linux-  allnoconfig
# make -s -j 48 ARCH=mips O=/kisskb/build/linus_mips-allnoconfig_mips CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/mips-linux/bin/mips-linux-  
/kisskb/src/arch/mips/vdso/Makefile:38: MIPS VDSO requires binutils >= 2.25
/kisskb/src/kernel/printk/printk.c: In function 'devkmsg_sysctl_set_loglvl':
/kisskb/src/kernel/printk/printk.c:186:16: warning: 'old' may be used uninitialized in this function [-Wuninitialized]
FIT description: Linux 5.0.0-rc4+
Created:         Tue Jan 29 07:01:06 2019
 Image 0 (kernel@0)
  Description:  Linux 5.0.0-rc4+
  Created:      Tue Jan 29 07:01:06 2019
  Type:         Kernel Image
  Compression:  gzip compressed
  Data Size:    624470 Bytes = 609.83 KiB = 0.60 MiB
  Architecture: MIPS
  OS:           Linux
  Load Address: 0x80100000
  Entry Point:  0x80215cc0
  Hash algo:    sha1
  Hash value:   b93d92e18d7c36158538e3b8229c1300ad0c80a2
 Default Configuration: 'conf@default'
 Configuration 0 (conf@default)
  Description:  Generic Linux kernel
  Kernel:       kernel@0
Completed OK
# rm -rf /kisskb/build/linus_mips-allnoconfig_mips
# Build took: 0:00:13.070313