# 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 # 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/gcc-4.6.3-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-gcc --version # < /opt/cross/kisskb/gcc-4.6.3-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-ld --version # < git log --format=%s --max-count=1 618d919cae2fcaadc752f27ddac8b939da8b441a # < make -s -j 10 ARCH=arm O=/kisskb/build/linus_simpad_defconfig_arm CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi- simpad_defconfig # make -s -j 10 ARCH=arm O=/kisskb/build/linus_simpad_defconfig_arm CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi- :1478:2: warning: #warning syscall pidfd_send_signal not implemented [-Wcpp] :1481:2: warning: #warning syscall io_uring_setup not implemented [-Wcpp] :1484:2: warning: #warning syscall io_uring_enter not implemented [-Wcpp] :1487:2: warning: #warning syscall io_uring_register not implemented [-Wcpp] /kisskb/src/kernel/printk/printk.c: In function 'devkmsg_sysctl_set_loglvl': /kisskb/src/kernel/printk/printk.c:187:16: warning: 'old' may be used uninitialized in this function [-Wuninitialized] /kisskb/src/kernel/rcu/srcutree.c: In function 'init_srcu_struct_fields': /kisskb/src/kernel/rcu/srcutree.c:121:34: warning: 'levelspread[]' may be used uninitialized in this function [-Wuninitialized] /kisskb/src/kernel/rcu/srcutree.c:88:6: note: 'levelspread[]' was declared here /kisskb/src/net/ipv4/ip_output.c: In function '__ip_append_data': /kisskb/src/include/linux/skbuff.h:1397:6: warning: 'extra_uref' may be used uninitialized in this function [-Wuninitialized] /kisskb/src/net/ipv4/ip_output.c:885:14: note: 'extra_uref' was declared here /kisskb/src/fs/proc/inode.c: In function 'proc_reg_open': /kisskb/src/include/linux/list.h:65:12: warning: 'pdeo' may be used uninitialized in this function [-Wuninitialized] /kisskb/src/fs/proc/inode.c:337:21: note: 'pdeo' was declared here Completed OK # rm -rf /kisskb/build/linus_simpad_defconfig_arm # Build took: 0:01:10.794788