linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Chunyan Zhang <zhang.chunyan@linaro.org>
Cc: kbuild-all@01.org, rostedt@goodmis.org,
	mathieu.poirier@linaro.org, alexander.shishkin@linux.intel.com,
	mingo@redhat.com, arnd@arndb.de, mike.leach@arm.com, tor@ti.com,
	philippe.langlais@st.com, nicolas.guion@st.com,
	felipe.balbi@linux.intel.com, zhang.lyra@gmail.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V4 1/3] tracing: add a possibility of exporting function trace to other places instead of ring buffer only
Date: Mon, 15 Aug 2016 21:03:22 +0800	[thread overview]
Message-ID: <201608152102.m6KoaCgL%fengguang.wu@intel.com> (raw)
In-Reply-To: <1471261803-1186-2-git-send-email-zhang.chunyan@linaro.org>

Hi Chunyan,

[auto build test WARNING on linus/master]
[also build test WARNING on v4.8-rc2 next-20160815]
[cannot apply to linux/master]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Chunyan-Zhang/tracing-add-a-possibility-of-exporting-function-trace-to-other-places-instead-of-ring-buffer-only/20160815-195631
reproduce:
        # apt-get install sparse
        make ARCH=x86_64 allmodconfig
        make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

   include/linux/compiler.h:230:8: sparse: attribute 'no_sanitize_address': unknown attribute
>> kernel/trace/trace.c:2173:23: sparse: incompatible types in comparison expression (different address spaces)
   kernel/trace/trace.c:2175:23: sparse: incompatible types in comparison expression (different address spaces)

vim +2173 kernel/trace/trace.c

  2157	static DEFINE_MUTEX(trace_export_lock);
  2158	
  2159	static struct trace_export trace_export_rb __read_mostly = {
  2160		.name		= "rb",
  2161		.commit	= trace_rb_commit,
  2162		.next		= NULL,
  2163	};
  2164	static struct trace_export *trace_exports_list __read_mostly = &trace_export_rb;
  2165	
  2166	inline void
  2167	trace_exports(struct trace_array *tr, struct ring_buffer_event *event)
  2168	{
  2169		struct trace_export *export;
  2170	
  2171		preempt_disable_notrace();
  2172	
> 2173		for (export = rcu_dereference_raw_notrace(trace_exports_list);
  2174		     export && export->commit;
  2175		     export = rcu_dereference_raw_notrace(export->next)) {
  2176			tr->export = export;
  2177			export->commit(tr, event);
  2178		}
  2179	
  2180		preempt_enable_notrace();
  2181	}

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

  reply	other threads:[~2016-08-15 13:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 11:50 [PATCH V4 0/3] Integration of function trace with System Trace IP blocks Chunyan Zhang
2016-08-15 11:50 ` [PATCH V4 1/3] tracing: add a possibility of exporting function trace to other places instead of ring buffer only Chunyan Zhang
2016-08-15 13:03   ` kbuild test robot [this message]
2016-08-18  7:48     ` Chunyan Zhang
2016-08-15 14:28   ` Steven Rostedt
2016-08-17 12:48     ` Chunyan Zhang
2016-08-17 14:11       ` Steven Rostedt
2016-08-18  9:22         ` Chunyan Zhang
2016-08-18 16:12           ` Steven Rostedt
2016-08-23  8:53             ` Chunyan Zhang
2016-08-15 11:50 ` [PATCH V4 2/3] stm class: ftrace: Add ftrace-export-over-stm driver Chunyan Zhang
2016-08-15 11:50 ` [PATCH V4 3/3] stm: Mark the functions of writing buffer with notrace Chunyan Zhang

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=201608152102.m6KoaCgL%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=felipe.balbi@linux.intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mike.leach@arm.com \
    --cc=mingo@redhat.com \
    --cc=nicolas.guion@st.com \
    --cc=philippe.langlais@st.com \
    --cc=rostedt@goodmis.org \
    --cc=tor@ti.com \
    --cc=zhang.chunyan@linaro.org \
    --cc=zhang.lyra@gmail.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;
as well as URLs for NNTP newsgroup(s).