Hi Stephane,

[auto build test ERROR on: tip/perf/core]
[also build test ERROR on: v4.3 next-20151103]

url:    
https://github.com/0day-ci/linux/commits/Stephane-Eranian/perf-fix-RCU-issues-with-cgroup-monitoring-mode/20151104-121512
config: parisc-allyesconfig (attached as .config)
reproduce:
        wget 
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
 -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=parisc 

All errors (new ones prefixed by >>):

   In file included from include/linux/trace_events.h:9:0,
                    from include/trace/syscall.h:6,
                    from include/linux/syscalls.h:81,
                    from kernel/events/core.c:34:
   include/linux/perf_event.h: In function 'perf_cgroup_from_task':
>> include/linux/perf_event.h:702:2: error: implicit declaration of function 
>> 'lockdep_is_held' [-Werror=implicit-function-declaration]
     bool safe = ctx ? lockdep_is_held(&ctx->lock) : true;
     ^
   include/linux/perf_event.h:702:7: warning: unused variable 'safe' 
[-Wunused-variable]
     bool safe = ctx ? lockdep_is_held(&ctx->lock) : true;
          ^
   cc1: some warnings being treated as errors

vim +/lockdep_is_held +702 include/linux/perf_event.h

   696   * this function. In other words, we cannot call this function
   697   * if there is no cgroup event for the current CPU context.
   698   */
   699  static inline struct perf_cgroup *
   700  perf_cgroup_from_task(struct task_struct *task, struct 
perf_event_context *ctx)
   701  {
 > 702          bool safe = ctx ? lockdep_is_held(&ctx->lock) : true;
   703          return container_of(task_css_check(task, perf_event_cgrp_id, 
safe),
   704                              struct perf_cgroup, css);
   705  }

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

Attachment: .config.gz
Description: Binary data

Reply via email to