All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v4 2/2] x86/purgatory: Make sure we fail the build if purgatory.ro has missing symbols
Date: Thu, 12 Mar 2020 13:56:40 +0800	[thread overview]
Message-ID: <202003121323.Rky4lxJO%lkp@intel.com> (raw)
In-Reply-To: <20200311214601.18141-3-hdegoede@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2423 bytes --]

Hi Hans,

I love your patch! Yet something to improve:

[auto build test ERROR on tip/x86/core]
[also build test ERROR on v5.6-rc5 next-20200311]
[cannot apply to tip/auto-latest bp/for-next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Hans-de-Goede/x86-purgatory-Make-sure-we-fail-the-build-if-purgatory-ro-has-missing-symbols/20200312-070856
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 248ed51048c40d36728e70914e38bffd7821da57
config: x86_64-randconfig-s0-20200312 (attached as .config)
compiler: gcc-7 (Debian 7.5.0-5) 7.5.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   ld: arch/x86/purgatory/purgatory.ro: in function `_GLOBAL__sub_I_00100_0_purgatory':
>> purgatory.c:(.text.startup+0xc): undefined reference to `__gcov_init'
   ld: arch/x86/purgatory/purgatory.ro: in function `_GLOBAL__sub_I_00100_0_sha256_update':
>> sha256.c:(.text.startup+0x2c): undefined reference to `__gcov_init'
   ld: arch/x86/purgatory/purgatory.ro: in function `_GLOBAL__sub_I_00100_0_memcmp':
>> string.c:(.text.startup+0x4c): undefined reference to `__gcov_init'
   ld: arch/x86/purgatory/purgatory.ro: in function `_GLOBAL__sub_D_00100_1_purgatory':
>> purgatory.c:(.text.exit+0x2): undefined reference to `__gcov_exit'
   ld: arch/x86/purgatory/purgatory.ro: in function `_GLOBAL__sub_D_00100_1_sha256_update':
>> sha256.c:(.text.exit+0x12): undefined reference to `__gcov_exit'
   ld: arch/x86/purgatory/purgatory.ro: in function `_GLOBAL__sub_D_00100_1_memcmp':
>> string.c:(.text.exit+0x22): undefined reference to `__gcov_exit'
>> ld: arch/x86/purgatory/purgatory.ro:(.data+0xc0): undefined reference to `__gcov_merge_add'
   ld: arch/x86/purgatory/purgatory.ro:(.data+0x21e0): undefined reference to `__gcov_merge_add'
   ld: arch/x86/purgatory/purgatory.ro:(.data+0x2780): undefined reference to `__gcov_merge_add'

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 32191 bytes --]

  parent reply	other threads:[~2020-03-12  5:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11 21:45 [PATCH v4 0/2] x86/purgatory: Make sure we fail the build if purgatory.ro has missing symbols Hans de Goede
2020-03-11 21:46 ` [PATCH v4 1/2] x86/purgatory: Fix missing ftrace_likely_update symbol Hans de Goede
2020-03-11 21:46 ` [PATCH v4 2/2] x86/purgatory: Make sure we fail the build if purgatory.ro has missing symbols Hans de Goede
2020-03-12  0:10   ` Arvind Sankar
2020-03-12 11:31     ` Hans de Goede
2020-03-12 11:42       ` Borislav Petkov
2020-03-12 11:58         ` Hans de Goede
2020-03-12 12:50           ` Borislav Petkov
2020-03-12 13:34             ` Hans de Goede
2020-03-12 14:25               ` Borislav Petkov
2020-03-12 14:38                 ` Hans de Goede
2020-03-12 14:49                   ` Borislav Petkov
2020-03-12 14:57                     ` Hans de Goede
2020-03-12 15:12                       ` Borislav Petkov
2020-03-13  4:42             ` Arvind Sankar
2020-03-13  4:58               ` Arvind Sankar
2020-03-13  5:15                 ` Arvind Sankar
2020-03-16 18:52                 ` Nick Desaulniers
2020-03-13 10:47               ` Hans de Goede
2020-03-13 18:06               ` Borislav Petkov
2020-03-12 17:46     ` Hans de Goede
2020-03-12 18:23       ` Arvind Sankar
2020-03-12  5:56   ` kbuild test robot [this message]
2020-03-12 13:59   ` kbuild test robot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=202003121323.Rky4lxJO%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.