# git rev-parse -q --verify 618d919cae2fcaadc752f27ddac8b939da8b441a^{commit}
618d919cae2fcaadc752f27ddac8b939da8b441a
already have revision, skipping fetch
# git checkout -q -f -B kisskb 618d919cae2fcaadc752f27ddac8b939da8b441a
# git clean -qxdf
# < git log -1
# commit 618d919cae2fcaadc752f27ddac8b939da8b441a
# Merge: 5512320c9f6f 2170a0d53bee
# Author: Linus Torvalds <torvalds@linux-foundation.org>
# Date:   Mon Apr 15 16:48:51 2019 -0700
# 
#     Merge tag 'libnvdimm-fixes-5.1-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
#     
#     Pull libnvdimm fixes from Dan Williams:
#      "I debated holding this back for the v5.2 merge window due to the size
#       of the "zero-key" changes, but affected users would benefit from
#       having the fixes sooner. It did not make sense to change the zero-key
#       semantic in isolation for the "secure-erase" command, but instead
#       include it for all security commands.
#     
#       The short background on the need for these changes is that some NVDIMM
#       platforms enable security with a default zero-key rather than let the
#       OS specify the initial key. This makes the security enabling that
#       landed in v5.0 unusable for some users.
#     
#       Summary:
#     
#        - Compatibility fix for nvdimm-security implementations with a
#          default zero-key.
#     
#        - Miscellaneous small fixes for out-of-bound accesses, cleanup after
#          initialization failures, and missing debug messages"
#     
#     * tag 'libnvdimm-fixes-5.1-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm:
#       tools/testing/nvdimm: Retain security state after overwrite
#       libnvdimm/pmem: fix a possible OOB access when read and write pmem
#       libnvdimm/security, acpi/nfit: unify zero-key for all security commands
#       libnvdimm/security: provide fix for secure-erase to use zero-key
#       libnvdimm/btt: Fix a kmemdup failure check
#       libnvdimm/namespace: Fix a potential NULL pointer dereference
#       acpi/nfit: Always dump _DSM output payload
# < /opt/cross/kisskb/fe-x86-64-core-i7-2017.05/bin/x86_64-linux-gcc --version
# < /opt/cross/kisskb/fe-x86-64-core-i7-2017.05/bin/x86_64-linux-ld --version
# < git log --format=%s --max-count=1 618d919cae2fcaadc752f27ddac8b939da8b441a
# < make -s -j 10 ARCH=um O=/kisskb/build/linus_um-defconfig_um-x86_64 CROSS_COMPILE=/opt/cross/kisskb/fe-x86-64-core-i7-2017.05/bin/x86_64-linux- SUBARCH=x86_64 defconfig
# make -s -j 10 ARCH=um O=/kisskb/build/linus_um-defconfig_um-x86_64 CROSS_COMPILE=/opt/cross/kisskb/fe-x86-64-core-i7-2017.05/bin/x86_64-linux- SUBARCH=x86_64 
/kisskb/src/arch/um/kernel/skas/uaccess.c: In function 'do_op_one_page':
/kisskb/src/arch/um/kernel/skas/uaccess.c:62:10: warning: unused variable 'buf' [-Wunused-variable]
  jmp_buf buf;
          ^
/kisskb/src/arch/um/os-Linux/umid.c: In function 'is_umdir_used':
/kisskb/src/arch/um/os-Linux/umid.c:138:2: warning: ISO C90 forbids variable length array 'file' [-Wvla]
  char file[strlen(uml_dir) + UMID_LEN + sizeof("/pid\0")];
  ^
/kisskb/src/arch/um/os-Linux/umid.c: In function 'create_pid_file':
/kisskb/src/arch/um/os-Linux/umid.c:213:2: warning: ISO C90 forbids variable length array 'file' [-Wvla]
  char file[strlen(uml_dir) + UMID_LEN + sizeof("/pid\0")];
  ^
/kisskb/src/arch/um/os-Linux/umid.c: In function 'remove_umid_dir':
/kisskb/src/arch/um/os-Linux/umid.c:388:2: warning: ISO C90 forbids variable length array 'dir' [-Wvla]
  char dir[strlen(uml_dir) + UMID_LEN + 1], err;
  ^
/kisskb/src/mm/mprotect.c: In function 'change_pte_range':
/kisskb/src/mm/mprotect.c:42:20: warning: unused variable 'mm' [-Wunused-variable]
  struct mm_struct *mm = vma->vm_mm;
                    ^
  LINK linux
Completed OK
# rm -rf /kisskb/build/linus_um-defconfig_um-x86_64
# Build took: 0:00:48.881690