Buildresult: linus-rand/arm64-randconfig/arm64-gcc5 built on Mar 12 2020, 06:04

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	OK
Date/Time:	Mar 12 2020, 06:04
Duration:	0:05:14.205544
Builder:	blade4b
Revision:	driver code: clarify and fix platform device DMA mask allocation (`e3a36eb6dfaeea8175c05d5915dcf0b939be6dab)`
Target:	linus-rand/arm64-randconfig/arm64-gcc5
Branch:	linus-rand
Compiler:	arm64-gcc5 (aarch64-linux-gcc.br_real (Buildroot 2016.11-git-00613-ge98b4dd) 5.4.0 / GNU ld (GNU Binutils) 2.25.1)
Config:	randconfig (download)
Log:	Download original Possible warnings (6) .config:4481:warning: override: reassigning to symbol PREVENT_FIRMWARE_BUILD drivers/block/null_blk_main.c:279:25: warning: 'new_value' is used uninitialized in this function [-Wuninitialized] drivers/block/null_blk_main.c:279:25: warning: 'new_value' is used uninitialized in this function [-Wuninitialized] drivers/block/null_blk_main.c:279:25: warning: 'new_value' is used uninitialized in this function [-Wuninitialized] drivers/block/null_blk_main.c:279:25: warning: 'new_value' is used uninitialized in this function [-Wuninitialized] drivers/block/null_blk_main.c:279:25: warning: 'new_value' is used uninitialized in this function [-Wuninitialized] Full Log # git rev-parse -q --verify e3a36eb6dfaeea8175c05d5915dcf0b939be6dab^{commit} e3a36eb6dfaeea8175c05d5915dcf0b939be6dab already have revision, skipping fetch # git checkout -q -f -B kisskb e3a36eb6dfaeea8175c05d5915dcf0b939be6dab # git clean -qxdf # < git log -1 # commit e3a36eb6dfaeea8175c05d5915dcf0b939be6dab # Author: Christoph Hellwig <hch@lst.de> # Date: Wed Mar 11 17:07:10 2020 +0100 # # driver code: clarify and fix platform device DMA mask allocation # # This does three inter-related things to clarify the usage of the # platform device dma_mask field. In the process, fix the bug introduced # by cdfee5623290 ("driver core: initialize a default DMA mask for # platform device") that caused Artem Tashkinov's laptop to not boot with # newer Fedora kernels. # # This does: # # - First off, rename the field to "platform_dma_mask" to make it # greppable. # # We have way too many different random fields called "dma_mask" in # various data structures, where some of them are actual masks, and # some of them are just pointers to the mask. And the structures all # have pointers to each other, or embed each other inside themselves, # and "pdev" sometimes means "platform device" and sometimes it means # "PCI device". # # So to make it clear in the code when you actually use this new field, # give it a unique name (it really should be something even more unique # like "platform_device_dma_mask", since it's per platform device, not # per platform, but that gets old really fast, and this is unique # enough in context). # # To further clarify when the field gets used, initialize it when we # actually start using it with the default value. # # - Then, use this field instead of the random one-off allocation in # platform_device_register_full() that is now unnecessary since we now # already have a perfectly fine allocation for it in the platform # device structure. # # - The above then allows us to fix the actual bug, where the error path # of platform_device_register_full() would unconditionally free the # platform device DMA allocation with 'kfree()'. # # That kfree() was dont regardless of whether the allocation had been # done earlier with the (now removed) kmalloc, or whether # setup_pdev_dma_masks() had already been used and the dma_mask pointer # pointed to the mask that was part of the platform device. # # It seems most people never triggered the error path, or only triggered # it from a call chain that set an explicit pdevinfo->dma_mask value (and # thus caused the unnecessary allocation that was "cleaned up" in the # error path) before calling platform_device_register_full(). # # Robin Murphy points out that in Artem's case the wdat_wdt driver failed # in platform_device_add(), and that was the one that had called # platform_device_register_full() with pdevinfo.dma_mask = 0, and would # have caused that kfree() of pdev.dma_mask corrupting the heap. # # A later unrelated kmalloc() then oopsed due to the heap corruption. # # Fixes: cdfee5623290 ("driver core: initialize a default DMA mask for platform device") # Reported-bisected-and-tested-by: Artem S. Tashkinov <aros@gmx.com> # Reviewed-by: Robin Murphy <robin.murphy@arm.com> # Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> # Signed-off-by: Christoph Hellwig <hch@lst.de> # Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> # < /opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-gcc --version # < /opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-ld --version # < git log --format=%s --max-count=1 e3a36eb6dfaeea8175c05d5915dcf0b939be6dab # < make -s -j 24 ARCH=arm64 O=/kisskb/build/linus-rand_arm64-randconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- randconfig KCONFIG_SEED=0x2FBF7D4B # Added to kconfig CONFIG_PREVENT_FIRMWARE_BUILD=y # < make -s -j 24 ARCH=arm64 O=/kisskb/build/linus-rand_arm64-randconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- help # make -s -j 24 ARCH=arm64 O=/kisskb/build/linus-rand_arm64-randconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- olddefconfig .config:4481:warning: override: reassigning to symbol PREVENT_FIRMWARE_BUILD # make -s -j 24 ARCH=arm64 O=/kisskb/build/linus-rand_arm64-randconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- arch/arm64/Makefile:27: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum arch/arm64/Makefile:27: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum /kisskb/src/drivers/block/null_blk_main.c: In function 'nullb_device_zoned_store': /kisskb/src/drivers/block/null_blk_main.c:279:25: warning: 'new_value' is used uninitialized in this function [-Wuninitialized] TYPE uninitialized_var(new_value); \ ^ In file included from /kisskb/src/include/linux/compiler_types.h:68:0, from <command-line>:0: /kisskb/src/drivers/block/null_blk_main.c:279:25: note: 'new_value' was declared here TYPE uninitialized_var(new_value); \ ^ /kisskb/src/include/linux/compiler-gcc.h:65:30: note: in definition of macro 'uninitialized_var' #define uninitialized_var(x) x = x ^ /kisskb/src/drivers/block/null_blk_main.c:325:1: note: in expansion of macro 'NULLB_DEVICE_ATTR' NULLB_DEVICE_ATTR(zoned, bool, NULL); ^ /kisskb/src/drivers/block/null_blk_main.c: In function 'nullb_device_discard_store': /kisskb/src/drivers/block/null_blk_main.c:279:25: warning: 'new_value' is used uninitialized in this function [-Wuninitialized] TYPE uninitialized_var(new_value); \ ^ In file included from /kisskb/src/include/linux/compiler_types.h:68:0, from <command-line>:0: /kisskb/src/drivers/block/null_blk_main.c:279:25: note: 'new_value' was declared here TYPE uninitialized_var(new_value); \ ^ /kisskb/src/include/linux/compiler-gcc.h:65:30: note: in definition of macro 'uninitialized_var' #define uninitialized_var(x) x = x ^ /kisskb/src/drivers/block/null_blk_main.c:322:1: note: in expansion of macro 'NULLB_DEVICE_ATTR' NULLB_DEVICE_ATTR(discard, bool, NULL); ^ /kisskb/src/drivers/block/null_blk_main.c: In function 'nullb_device_memory_backed_store': /kisskb/src/drivers/block/null_blk_main.c:279:25: warning: 'new_value' is used uninitialized in this function [-Wuninitialized] TYPE uninitialized_var(new_value); \ ^ In file included from /kisskb/src/include/linux/compiler_types.h:68:0, from <command-line>:0: /kisskb/src/drivers/block/null_blk_main.c:279:25: note: 'new_value' was declared here TYPE uninitialized_var(new_value); \ ^ /kisskb/src/include/linux/compiler-gcc.h:65:30: note: in definition of macro 'uninitialized_var' #define uninitialized_var(x) x = x ^ /kisskb/src/drivers/block/null_blk_main.c:321:1: note: in expansion of macro 'NULLB_DEVICE_ATTR' NULLB_DEVICE_ATTR(memory_backed, bool, NULL); ^ /kisskb/src/drivers/block/null_blk_main.c: In function 'nullb_device_use_per_node_hctx_store': /kisskb/src/drivers/block/null_blk_main.c:279:25: warning: 'new_value' is used uninitialized in this function [-Wuninitialized] TYPE uninitialized_var(new_value); \ ^ In file included from /kisskb/src/include/linux/compiler_types.h:68:0, from <command-line>:0: /kisskb/src/drivers/block/null_blk_main.c:279:25: note: 'new_value' was declared here TYPE uninitialized_var(new_value); \ ^ /kisskb/src/include/linux/compiler-gcc.h:65:30: note: in definition of macro 'uninitialized_var' #define uninitialized_var(x) x = x ^ /kisskb/src/drivers/block/null_blk_main.c:320:1: note: in expansion of macro 'NULLB_DEVICE_ATTR' NULLB_DEVICE_ATTR(use_per_node_hctx, bool, NULL); ^ /kisskb/src/drivers/block/null_blk_main.c: In function 'nullb_device_blocking_store': /kisskb/src/drivers/block/null_blk_main.c:279:25: warning: 'new_value' is used uninitialized in this function [-Wuninitialized] TYPE uninitialized_var(new_value); \ ^ In file included from /kisskb/src/include/linux/compiler_types.h:68:0, from <command-line>:0: /kisskb/src/drivers/block/null_blk_main.c:279:25: note: 'new_value' was declared here TYPE uninitialized_var(new_value); \ ^ /kisskb/src/include/linux/compiler-gcc.h:65:30: note: in definition of macro 'uninitialized_var' #define uninitialized_var(x) x = x ^ /kisskb/src/drivers/block/null_blk_main.c:319:1: note: in expansion of macro 'NULLB_DEVICE_ATTR' NULLB_DEVICE_ATTR(blocking, bool, NULL); ^ Completed OK # rm -rf /kisskb/build/linus-rand_arm64-randconfig_arm64-gcc5.4 # Build took: 0:05:14.205544

© Michael Ellerman 2006-2018.