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: [RFC][PATCH 3/4] x86/entry: Remove debug IST frobbing
Date: Mon, 25 May 2020 20:33:53 +0800	[thread overview]
Message-ID: <202005252029.iTfdizIE%lkp@intel.com> (raw)
In-Reply-To: <20200522204943.350442553@infradead.org>

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

Hi Peter,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on tip/auto-latest]
[cannot apply to tip/x86/core luto/next v5.7-rc7 next-20200522]
[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/Peter-Zijlstra/x86-entry-disallow-DB-more/20200523-045236
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 82c5ba14c091497fc5d79ee017f962e50c3f69ac
config: x86_64-rhel-7.6-kselftests (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build):
        # save the attached .config to linux build tree
        make W=1 ARCH=x86_64 

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

All errors (new ones prefixed by >>, old ones prefixed by <<):

ld: arch/x86/entry/entry_64.o: in function `asm_exc_debug':
>> arch/x86/include/asm/idtentry.h:368: undefined reference to `debug_stack_set_zero'
>> ld: arch/x86/include/asm/idtentry.h:368: undefined reference to `debug_stack_reset'
ld: arch/x86/entry/entry_64.o: in function `paranoid_exit':
>> arch/x86/entry/entry_64.S:1281: undefined reference to `debug_stack_set_zero'
>> ld: arch/x86/entry/entry_64.S:1281: undefined reference to `debug_stack_reset'
>> ld: arch/x86/entry/entry_64.S:1290: undefined reference to `debug_stack_set_zero'
ld: arch/x86/entry/entry_64.S:1290: undefined reference to `debug_stack_reset'
Segmentation fault
.btf.vmlinux.bin.o: file not recognized: file format not recognized

vim +368 arch/x86/include/asm/idtentry.h

b209b183b6db50 Thomas Gleixner 2020-02-25  366  
c087b87b146916 Thomas Gleixner 2020-02-25  367  /* #DB */
c087b87b146916 Thomas Gleixner 2020-02-25 @368  DECLARE_IDTENTRY_DEBUG(X86_TRAP_DB,	exc_debug);
c087b87b146916 Thomas Gleixner 2020-02-25  369  DECLARE_IDTENTRY_XEN(X86_TRAP_DB,	debug);
c087b87b146916 Thomas Gleixner 2020-02-25  370  

:::::: The code at line 368 was first introduced by commit
:::::: c087b87b1469166dbb0d757c7d79fecf14a90a0a x86/entry: Convert Debug exception to IDTENTRY_DB

:::::: TO: Thomas Gleixner <tglx@linutronix.de>
:::::: CC: Thomas Gleixner <tglx@linutronix.de>

---
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: 49332 bytes --]

  parent reply	other threads:[~2020-05-25 12:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 20:47 [RFC][PATCH 0/4] x86/entry: disallow #DB more Peter Zijlstra
2020-05-22 20:47 ` [RFC][PATCH 1/4] x86/entry: Introduce local_db_{rave,restore}() Peter Zijlstra
2020-05-22 20:47 ` [RFC][PATCH 2/4] x86/entry, nmi: Disable #DB Peter Zijlstra
2020-05-22 20:47 ` [RFC][PATCH 3/4] x86/entry: Remove debug IST frobbing Peter Zijlstra
2020-05-25 11:33   ` kbuild test robot
2020-05-25 12:33   ` kbuild test robot [this message]
2020-05-22 20:47 ` [RFC][PATCH 4/4] x86/entry, mce: Disallow #DB during #MC Peter Zijlstra
2020-05-22 22:13 ` [RFC][PATCH 0/4] x86/entry: disallow #DB more Andy Lutomirski
2020-05-22 22:20   ` Sean Christopherson
2020-05-22 22:43     ` Andy Lutomirski
2020-05-23 12:59   ` Peter Zijlstra
2020-05-23 21:32     ` Peter Zijlstra
2020-05-25 10:02       ` Rasmus Villemoes
2020-05-25 10:40         ` Peter Zijlstra
2020-05-25 11:01           ` Peter Zijlstra
2020-05-25 17:19             ` Andy Lutomirski
2020-05-25 18:08               ` Peter Zijlstra

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=202005252029.iTfdizIE%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.