* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This automated bisection report was sent to you on the basis  *
* that you may be involved with the breaking commit it has      *
* found.  No manual investigation has been done to verify it,   *
* and the root cause of the problem may be somewhere else.      *
*                                                               *
* If you do send a fix, please include this trailer:            *
*   Reported-by: "kernelci.org bot" <b...@kernelci.org>          *
*                                                               *
* Hope this helps!                                              *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

mainline/master boot bisection: v5.3-12562-g7897c04ad09f on bcm2836-rpi-2-b

Summary:
  Start:      7897c04ad09f Merge tag 'trace-v5.4-2' of 
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
  Details:    https://kernelci.org/boot/id/5d8d446459b51415c1f1224d
  Plain log:  
https://storage.kernelci.org//mainline/master/v5.3-12562-g7897c04ad09f/arm/bcm2835_defconfig/gcc-8/lab-collabora/boot-bcm2836-rpi-2-b.txt
  HTML log:   
https://storage.kernelci.org//mainline/master/v5.3-12562-g7897c04ad09f/arm/bcm2835_defconfig/gcc-8/lab-collabora/boot-bcm2836-rpi-2-b.html
  Result:     ac7c3e4ff401 compiler: enable CONFIG_OPTIMIZE_INLINING forcibly

Checks:
  revert:     PASS
  verify:     PASS

Parameters:
  Tree:       mainline
  URL:        git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
  Branch:     master
  Target:     bcm2836-rpi-2-b
  CPU arch:   arm
  Lab:        lab-collabora
  Compiler:   gcc-8
  Config:     bcm2835_defconfig
  Test suite: boot

Breaking commit found:

-------------------------------------------------------------------------------
commit ac7c3e4ff401b304489a031938dbeaab585bfe0a
Author: Masahiro Yamada <yamada.masah...@socionext.com>
Date:   Wed Sep 25 16:47:42 2019 -0700

    compiler: enable CONFIG_OPTIMIZE_INLINING forcibly
    
    Commit 9012d011660e ("compiler: allow all arches to enable
    CONFIG_OPTIMIZE_INLINING") allowed all architectures to enable this
    option.  A couple of build errors were reported by randconfig, but all of
    them have been ironed out.
    
    Towards the goal of removing CONFIG_OPTIMIZE_INLINING entirely (and it
    will simplify the 'inline' macro in compiler_types.h), this commit changes
    it to always-on option.  Going forward, the compiler will always be
    allowed to not inline functions marked 'inline'.
    
    This is not a problem for x86 since it has been long used by
    arch/x86/configs/{x86_64,i386}_defconfig.
    
    I am keeping the config option just in case any problem crops up for other
    architectures.
    
    The code clean-up will be done after confirming this is solid.
    
    Link: 
http://lkml.kernel.org/r/20190830034304.24259-1-yamada.masah...@socionext.com
    Signed-off-by: Masahiro Yamada <yamada.masah...@socionext.com>
    Acked-by: Nick Desaulniers <ndesaulni...@google.com>
    Cc: Ingo Molnar <mi...@redhat.com>
    Cc: Borislav Petkov <b...@alien8.de>
    Cc: Miguel Ojeda <miguel.ojeda.sando...@gmail.com>
    Signed-off-by: Andrew Morton <a...@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torva...@linux-foundation.org>

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 6b1b1703a646..93d97f9b0157 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -311,7 +311,7 @@ config HEADERS_CHECK
          relevant for userspace, say 'Y'.
 
 config OPTIMIZE_INLINING
-       bool "Allow compiler to uninline functions marked 'inline'"
+       def_bool y
        help
          This option determines if the kernel forces gcc to inline the 
functions
          developers have marked 'inline'. Doing so takes away freedom from gcc 
to
@@ -322,8 +322,6 @@ config OPTIMIZE_INLINING
          decision will become the default in the future. Until then this option
          is there to test gcc for this.
 
-         If unsure, say N.
-
 config DEBUG_SECTION_MISMATCH
        bool "Enable full Section mismatch analysis"
        help
-------------------------------------------------------------------------------


Git bisection log:

-------------------------------------------------------------------------------
git bisect start
# good: [f41def397161053eb0d3ed6861ef65985efbf293] Merge tag 'ceph-for-5.4-rc1' 
of git://github.com/ceph/ceph-client
git bisect good f41def397161053eb0d3ed6861ef65985efbf293
# bad: [7897c04ad09f815aea1f2dbb05825887d4494a74] Merge tag 'trace-v5.4-2' of 
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
git bisect bad 7897c04ad09f815aea1f2dbb05825887d4494a74
# bad: [ec56103e18c7590303c69329dd4aaadf8a898c19] Merge tag 
'for-linus-5.4-rc1-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip
git bisect bad ec56103e18c7590303c69329dd4aaadf8a898c19
# bad: [da036ae147624b70f7d3784ff3a53bd4fda20d2a] scripts/gdb: handle split 
debug
git bisect bad da036ae147624b70f7d3784ff3a53bd4fda20d2a
# good: [5a7f4455ad321400e1361ab94fd6858c5b2fe0cf] checkpatch: remove obsolete 
period from "ambiguous SHA1" query
git bisect good 5a7f4455ad321400e1361ab94fd6858c5b2fe0cf
# good: [3e9fd5a48cb7b0ef93be097c2c1066738d37f5b7] fs/reiserfs/journal.c: 
remove set but not used variable
git bisect good 3e9fd5a48cb7b0ef93be097c2c1066738d37f5b7
# good: [7c3a6aedcd6aae0a32a527e68669f7dd667492d1] kexec: bail out upon SIGKILL 
when allocating memory.
git bisect good 7c3a6aedcd6aae0a32a527e68669f7dd667492d1
# good: [9dd819a15162f8f82a6001b090caa38c18297b39] uaccess: add missing 
__must_check attributes
git bisect good 9dd819a15162f8f82a6001b090caa38c18297b39
# bad: [7d92bda271ddcbb2d1be2f82733dcb9bf8378010] kgdb: don't use a notifier to 
enter kgdb at panic; call directly
git bisect bad 7d92bda271ddcbb2d1be2f82733dcb9bf8378010
# bad: [ac7c3e4ff401b304489a031938dbeaab585bfe0a] compiler: enable 
CONFIG_OPTIMIZE_INLINING forcibly
git bisect bad ac7c3e4ff401b304489a031938dbeaab585bfe0a
# first bad commit: [ac7c3e4ff401b304489a031938dbeaab585bfe0a] compiler: enable 
CONFIG_OPTIMIZE_INLINING forcibly
-------------------------------------------------------------------------------

Reply via email to