# git rev-parse -q --verify e6506eb241871d68647c53cb6d0a16299550ae97^{commit} e6506eb241871d68647c53cb6d0a16299550ae97 already have revision, skipping fetch # git checkout -q -f -B kisskb e6506eb241871d68647c53cb6d0a16299550ae97 # git clean -qxdf # < git log -1 # commit e6506eb241871d68647c53cb6d0a16299550ae97 # Merge: 9d38cd0 45dd9b0 # Author: Linus Torvalds # Date: Wed May 16 16:45:23 2018 -0700 # # Merge tag 'trace-v4.17-rc4-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace # # Pull tracing fix from Steven Rostedt: # "Some of the ftrace internal events use a zero for a data size of a # field event. This is increasingly important for the histogram trigger # work that is being extended. # # While auditing trace events, I found that a couple of the xen events # were used as just marking that a function was called, by creating a # static array of size zero. This can play havoc with the tracing # features if these events are used, because a zero size of a static # array is denoted as a special nul terminated dynamic array (this is # what the trace_marker code uses). But since the xen events have no # size, they are not nul terminated, and unexpected results may occur. # # As trace events were never intended on being a marker to denote that a # function was hit or not, especially since function tracing and kprobes # can trivially do the same, the best course of action is to simply # remove these events" # # * tag 'trace-v4.17-rc4-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace: # tracing/x86/xen: Remove zero data size trace events trace_xen_mmu_flush_tlb{_all} # < /opt/cross/kisskb/gcc-5.2.0-nolibc/powerpc64le-linux/bin/powerpc64le-linux-gcc --version # < git log --format=%s --max-count=1 e6506eb241871d68647c53cb6d0a16299550ae97 # < make -s -j 8 ARCH=powerpc O=/kisskb/build/linus_allmodconfig+ppc64le_ppc64le CROSS_COMPILE=/opt/cross/kisskb/gcc-5.2.0-nolibc/powerpc64le-linux/bin/powerpc64le-linux- allmodconfig # Added to kconfig CONFIG_CPU_LITTLE_ENDIAN=y # Added to kconfig CONFIG_BUILD_DOCSRC=n # Added to kconfig CONFIG_MODULE_SIG=n # Added to kconfig CONFIG_SAMPLES=n # yes \n | make -s -j 8 ARCH=powerpc O=/kisskb/build/linus_allmodconfig+ppc64le_ppc64le CROSS_COMPILE=/opt/cross/kisskb/gcc-5.2.0-nolibc/powerpc64le-linux/bin/powerpc64le-linux- oldconfig yes: standard output: Broken pipe yes: write error # make -s -j 8 ARCH=powerpc O=/kisskb/build/linus_allmodconfig+ppc64le_ppc64le CROSS_COMPILE=/opt/cross/kisskb/gcc-5.2.0-nolibc/powerpc64le-linux/bin/powerpc64le-linux- In file included from /kisskb/src/include/linux/io.h:25:0, from /kisskb/src/include/linux/of_address.h:7, from /kisskb/src/drivers/ata/ahci_qoriq.c:18: /kisskb/src/drivers/ata/ahci_qoriq.c: In function 'ahci_qoriq_hardreset': /kisskb/src/arch/powerpc/include/asm/io.h:160:2: warning: 'px_is' may be used uninitialized in this function [-Wmaybe-uninitialized] __asm__ __volatile__("sync;"#insn"%U0%X0 %1,%0" \ ^ /kisskb/src/drivers/ata/ahci_qoriq.c:86:14: note: 'px_is' was declared here u32 px_cmd, px_is, px_val; ^ In file included from /kisskb/src/include/linux/io.h:25:0, from /kisskb/src/include/linux/of_address.h:7, from /kisskb/src/drivers/ata/ahci_qoriq.c:18: /kisskb/src/arch/powerpc/include/asm/io.h:160:2: warning: 'px_cmd' may be used uninitialized in this function [-Wmaybe-uninitialized] __asm__ __volatile__("sync;"#insn"%U0%X0 %1,%0" \ ^ /kisskb/src/drivers/ata/ahci_qoriq.c:86:6: note: 'px_cmd' was declared here u32 px_cmd, px_is, px_val; ^ WARNING: vmlinux.o(.text+0x3664): Section mismatch in reference from the variable __boot_from_prom to the function .init.text:prom_init() The function __boot_from_prom() references the function __init prom_init(). This is often because __boot_from_prom lacks a __init annotation or the annotation of prom_init is wrong. WARNING: vmlinux.o(.text+0x3944): Section mismatch in reference from the variable start_here_multiplatform to the function .init.text:early_setup() The function start_here_multiplatform() references the function __init early_setup(). This is often because start_here_multiplatform lacks a __init annotation or the annotation of early_setup is wrong. WARNING: vmlinux.o(.text+0x3978): Section mismatch in reference from the variable start_here_common to the function .init.text:start_kernel() The function start_here_common() references the function __init start_kernel(). This is often because start_here_common lacks a __init annotation or the annotation of start_kernel is wrong. WARNING: vmlinux.o(.text+0x35bc2c): Section mismatch in reference from the function devm_memremap_pages() to the function .meminit.text:arch_add_memory() The function devm_memremap_pages() references the function __meminit arch_add_memory(). This is often because devm_memremap_pages lacks a __meminit annotation or the annotation of arch_add_memory is wrong. WARNING: vmlinux.o(.text+0x35c508): Section mismatch in reference from the function devm_memremap_pages_release() to the function .meminit.text:arch_remove_memory() The function devm_memremap_pages_release() references the function __meminit arch_remove_memory(). This is often because devm_memremap_pages_release lacks a __meminit annotation or the annotation of arch_remove_memory is wrong. WARNING: vmlinux.o(.text+0x49933c): Section mismatch in reference from the function hmm_devmem_release() to the function .meminit.text:arch_remove_memory() The function hmm_devmem_release() references the function __meminit arch_remove_memory(). This is often because hmm_devmem_release lacks a __meminit annotation or the annotation of arch_remove_memory is wrong. WARNING: vmlinux.o(.text+0x4996b0): Section mismatch in reference from the function hmm_devmem_pages_create() to the function .meminit.text:arch_add_memory() The function hmm_devmem_pages_create() references the function __meminit arch_add_memory(). This is often because hmm_devmem_pages_create lacks a __meminit annotation or the annotation of arch_add_memory is wrong. Completed OK # rm -rf /kisskb/build/linus_allmodconfig+ppc64le_ppc64le # Build took: 0:20:18.957004