public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Waiman Long <longman@redhat.com>
Cc: kbuild-all@lists.01.org, Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Will Deacon <will.deacon@arm.com>,
	linux-kernel@vger.kernel.org,
	Bart Van Assche <bvanassche@acm.org>,
	Waiman Long <longman@redhat.com>
Subject: Re: [PATCH v4 6/7] locking/lockdep: Reuse freed chain_hlocks entries
Date: Fri, 24 Jan 2020 19:57:09 +0800	[thread overview]
Message-ID: <202001241955.O97gsbJl%lkp@intel.com> (raw)
In-Reply-To: <20200121154009.11993-7-longman@redhat.com>

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

Hi Waiman,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on tip/locking/core]
[also build test ERROR on tip/auto-latest arm-perf/for-next/perf v5.5-rc7 next-20200121]
[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/Waiman-Long/locking-lockdep-Reuse-zapped-chain_hlocks-entries/20200124-085419
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git f5bfdc8e3947a7ae489cf8ae9cfd6b3fb357b952
config: xtensa-randconfig-a001-20200124 (attached as .config)
compiler: xtensa-linux-gcc (GCC) 7.5.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=7.5.0 make.cross ARCH=xtensa 

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

All errors (new ones prefixed by >>):

   kernel/locking/lockdep.o: In function `arch_local_irq_restore':
>> arch/xtensa/include/asm/irqflags.h:66: undefined reference to `init_chain_block_buckets'
   kernel/locking/lockdep.o: In function `__lock_pin_lock':
   kernel/locking/lockdep.c:4565: undefined reference to `init_chain_block_buckets'
   kernel/locking/lockdep_proc.o: In function `l_stop':
   kernel/locking/lockdep_proc.c:39: undefined reference to `nr_zapped_lock_chains'
>> kernel/locking/lockdep_proc.c:39: undefined reference to `nr_large_chain_blocks'

vim +66 arch/xtensa/include/asm/irqflags.h

df9ee29270c11d David Howells 2010-10-07  63  
df9ee29270c11d David Howells 2010-10-07  64  static inline void arch_local_irq_restore(unsigned long flags)
df9ee29270c11d David Howells 2010-10-07  65  {
bc5378fcba9743 Max Filippov  2012-10-15 @66  	asm volatile("wsr %0, ps; rsync"
df9ee29270c11d David Howells 2010-10-07  67  		     :: "a" (flags) : "memory");
df9ee29270c11d David Howells 2010-10-07  68  }
df9ee29270c11d David Howells 2010-10-07  69  

:::::: The code at line 66 was first introduced by commit
:::::: bc5378fcba974317f9657c4fdc78af227e1e1068 xtensa: reorganize SR referencing

:::::: TO: Max Filippov <jcmvbkbc@gmail.com>
:::::: CC: Chris Zankel <chris@zankel.net>

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation

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

  reply	other threads:[~2020-01-24 11:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21 15:40 [PATCH v4 0/7] locking/lockdep: Reuse zapped chain_hlocks entries Waiman Long
2020-01-21 15:40 ` [PATCH v4 1/7] locking/lockdep: Decrement irq context counters when removing lock chain Waiman Long
2020-01-21 15:40 ` [PATCH v4 2/7] locking/lockdep: Display irq_context names in /proc/lockdep_chains Waiman Long
2020-01-21 15:40 ` [PATCH v4 3/7] locking/lockdep: Track number of zapped classes Waiman Long
2020-01-21 15:40 ` [PATCH v4 4/7] locking/lockdep: Throw away all lock chains with zapped class Waiman Long
2020-01-21 15:40 ` [PATCH v4 5/7] locking/lockdep: Track number of zapped lock chains Waiman Long
2020-01-24 13:18   ` kbuild test robot
2020-01-24 20:15   ` kbuild test robot
2020-01-21 15:40 ` [PATCH v4 6/7] locking/lockdep: Reuse freed chain_hlocks entries Waiman Long
2020-01-24 11:57   ` kbuild test robot [this message]
2020-01-21 15:40 ` [PATCH v4 7/7] locking/lockdep: Add a fast path for chain_hlocks allocation Waiman Long

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=202001241955.O97gsbJl%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bvanassche@acm.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=will.deacon@arm.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox