All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>, davem@davemloft.net
Cc: kbuild-all@lists.01.org, daniel@iogearbox.net,
	netdev@vger.kernel.org, bpf@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v2 bpf-next 2/4] bpf: Introduce sleepable BPF programs
Date: Sun, 31 May 2020 10:19:36 +0800	[thread overview]
Message-ID: <202005311049.SVdA9Hza%lkp@intel.com> (raw)
In-Reply-To: <20200529043839.15824-3-alexei.starovoitov@gmail.com>

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

Hi Alexei,

I love your patch! Yet something to improve:

[auto build test ERROR on net-next/master]
[also build test ERROR on v5.7-rc7 next-20200529]
[cannot apply to bpf-next/master bpf/master net/master]
[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/Alexei-Starovoitov/bpf-Introduce-minimal-support-for-sleepable-progs/20200531-055259
base:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git bc183dec08f9cb177cf5206a010b7a9e7b22e567
config: microblaze-randconfig-c003-20200531 (attached as .config)
compiler: microblaze-linux-gcc (GCC) 9.3.0

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 <<):

microblaze-linux-ld: kernel/bpf/syscall.o: in function `__bpf_prog_put_noref':
kernel/bpf/syscall.c:1729: undefined reference to `bpf_srcu'
microblaze-linux-ld: kernel/bpf/hashtab.o: in function `lock_is_held':
>> include/linux/lockdep.h:406: undefined reference to `bpf_srcu'
microblaze-linux-ld: kernel/bpf/hashtab.o: in function `htab_map_free':
kernel/bpf/hashtab.c:1305: undefined reference to `bpf_srcu'
microblaze-linux-ld: kernel/bpf/hashtab.o: in function `lock_is_held':
>> include/linux/lockdep.h:406: undefined reference to `bpf_srcu'
>> microblaze-linux-ld: include/linux/lockdep.h:406: undefined reference to `bpf_srcu'
microblaze-linux-ld: kernel/bpf/hashtab.o:include/linux/lockdep.h:406: more undefined references to `bpf_srcu' follow

vim +406 include/linux/lockdep.h

f8319483f57f1c Peter Zijlstra 2016-11-30  403  
08f36ff642342f Matthew Wilcox 2018-01-17  404  static inline int lock_is_held(const struct lockdep_map *lock)
f8319483f57f1c Peter Zijlstra 2016-11-30  405  {
f8319483f57f1c Peter Zijlstra 2016-11-30 @406  	return lock_is_held_type(lock, -1);
f8319483f57f1c Peter Zijlstra 2016-11-30  407  }
f607c668577481 Peter Zijlstra 2009-07-20  408  

:::::: The code at line 406 was first introduced by commit
:::::: f8319483f57f1ca22370f4150bb990aca7728a67 locking/lockdep: Provide a type check for lock_is_held

:::::: TO: Peter Zijlstra <peterz@infradead.org>
:::::: CC: Dave Chinner <david@fromorbit.com>

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

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

WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v2 bpf-next 2/4] bpf: Introduce sleepable BPF programs
Date: Sun, 31 May 2020 10:19:36 +0800	[thread overview]
Message-ID: <202005311049.SVdA9Hza%lkp@intel.com> (raw)
In-Reply-To: <20200529043839.15824-3-alexei.starovoitov@gmail.com>

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

Hi Alexei,

I love your patch! Yet something to improve:

[auto build test ERROR on net-next/master]
[also build test ERROR on v5.7-rc7 next-20200529]
[cannot apply to bpf-next/master bpf/master net/master]
[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/Alexei-Starovoitov/bpf-Introduce-minimal-support-for-sleepable-progs/20200531-055259
base:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git bc183dec08f9cb177cf5206a010b7a9e7b22e567
config: microblaze-randconfig-c003-20200531 (attached as .config)
compiler: microblaze-linux-gcc (GCC) 9.3.0

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 <<):

microblaze-linux-ld: kernel/bpf/syscall.o: in function `__bpf_prog_put_noref':
kernel/bpf/syscall.c:1729: undefined reference to `bpf_srcu'
microblaze-linux-ld: kernel/bpf/hashtab.o: in function `lock_is_held':
>> include/linux/lockdep.h:406: undefined reference to `bpf_srcu'
microblaze-linux-ld: kernel/bpf/hashtab.o: in function `htab_map_free':
kernel/bpf/hashtab.c:1305: undefined reference to `bpf_srcu'
microblaze-linux-ld: kernel/bpf/hashtab.o: in function `lock_is_held':
>> include/linux/lockdep.h:406: undefined reference to `bpf_srcu'
>> microblaze-linux-ld: include/linux/lockdep.h:406: undefined reference to `bpf_srcu'
microblaze-linux-ld: kernel/bpf/hashtab.o:include/linux/lockdep.h:406: more undefined references to `bpf_srcu' follow

vim +406 include/linux/lockdep.h

f8319483f57f1c Peter Zijlstra 2016-11-30  403  
08f36ff642342f Matthew Wilcox 2018-01-17  404  static inline int lock_is_held(const struct lockdep_map *lock)
f8319483f57f1c Peter Zijlstra 2016-11-30  405  {
f8319483f57f1c Peter Zijlstra 2016-11-30 @406  	return lock_is_held_type(lock, -1);
f8319483f57f1c Peter Zijlstra 2016-11-30  407  }
f607c668577481 Peter Zijlstra 2009-07-20  408  

:::::: The code at line 406 was first introduced by commit
:::::: f8319483f57f1ca22370f4150bb990aca7728a67 locking/lockdep: Provide a type check for lock_is_held

:::::: TO: Peter Zijlstra <peterz@infradead.org>
:::::: CC: Dave Chinner <david@fromorbit.com>

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

  parent reply	other threads:[~2020-05-31  2:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29  4:38 [PATCH v2 bpf-next 0/4] bpf: Introduce minimal support for sleepable progs Alexei Starovoitov
2020-05-29  4:38 ` [PATCH v2 bpf-next 1/4] bpf: Fix use-after-free in fmod_ret check Alexei Starovoitov
2020-05-29  4:38 ` [PATCH v2 bpf-next 2/4] bpf: Introduce sleepable BPF programs Alexei Starovoitov
2020-05-29  8:25   ` Andrii Nakryiko
2020-05-29 20:12     ` Alexei Starovoitov
2020-05-29 20:38       ` Andrii Nakryiko
2020-05-29 20:52         ` Alexei Starovoitov
2020-05-31  2:19   ` kbuild test robot [this message]
2020-05-31  2:19     ` kbuild test robot
2020-05-31  4:33   ` kbuild test robot
2020-05-31  4:33     ` kbuild test robot
2020-05-29  4:38 ` [PATCH v2 bpf-next 3/4] libbpf: support sleepable progs Alexei Starovoitov
2020-05-29  4:38 ` [PATCH v2 bpf-next 4/4] selftests/bpf: basic sleepable tests Alexei Starovoitov

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=202005311049.SVdA9Hza%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=kbuild-all@lists.01.org \
    --cc=kernel-team@fb.com \
    --cc=netdev@vger.kernel.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.