From: kbuild test robot <lkp@intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
peterz@infradead.org, mingo@elte.hu, ak@linux.intel.com,
edumazet@google.com, acme@redhat.com
Subject: Re: [PATCH v3] perf: fix RCU issues with cgroup monitoring mode
Date: Wed, 4 Nov 2015 12:41:16 +0800 [thread overview]
Message-ID: <201511041253.oUo3gZtk%fengguang.wu@intel.com> (raw)
In-Reply-To: <20151104041219.GA12969@thinkpad>
[-- Attachment #1: Type: text/plain, Size: 1957 bytes --]
Hi Stephane,
[auto build test WARNING on: tip/perf/core]
[also build test WARNING 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: i386-randconfig-i0-201544 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (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 init/main.c:18:
include/linux/perf_event.h: In function 'perf_cgroup_from_task':
>> include/linux/perf_event.h:702:7: warning: unused variable 'safe' [-Wunused-variable]
bool safe = ctx ? lockdep_is_held(&ctx->lock) : true;
^
vim +/safe +702 include/linux/perf_event.h
686 u64 timestamp;
687 };
688
689 struct perf_cgroup {
690 struct cgroup_subsys_state css;
691 struct perf_cgroup_info __percpu *info;
692 };
693
694 /*
695 * Must ensure cgroup is pinned (css_get) before calling
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 }
706 #endif /* CONFIG_CGROUP_PERF */
707
708 #ifdef CONFIG_PERF_EVENTS
709
710 extern void *perf_aux_output_begin(struct perf_output_handle *handle,
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 22679 bytes --]
next prev parent reply other threads:[~2015-11-04 4:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 4:12 [PATCH v3] perf: fix RCU issues with cgroup monitoring mode Stephane Eranian
2015-11-04 4:29 ` kbuild test robot
2015-11-04 4:41 ` kbuild test robot [this message]
2015-11-04 15:53 ` 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=201511041253.oUo3gZtk%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=edumazet@google.com \
--cc=eranian@google.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).