mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Chunyu Hu <chuhu@redhat.com>
Cc: kbuild-all@01.org, rostedt@goodmis.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: Fix oops caused by graph notrace filter
Date: Tue, 21 Jun 2016 20:39:22 +0800	[thread overview]
Message-ID: <201606212034.rXT4171b%fengguang.wu@intel.com> (raw)
In-Reply-To: <1466506666-28804-1-git-send-email-chuhu@redhat.com>

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

Hi,

[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.7-rc4 next-20160621]
[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/Chunyu-Hu/tracing-Fix-oops-caused-by-graph-notrace-filter/20160621-191210
config: i386-randconfig-r0-201625 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   kernel/built-in.o: In function `irqsoff_tracer_reset':
>> trace_irqsoff.c:(.text+0x8d38f): undefined reference to `ftrace_graph_ignore_notrace'
   kernel/built-in.o: In function `__irqsoff_tracer_init':
   trace_irqsoff.c:(.text+0x8d3fa): undefined reference to `ftrace_graph_ignore_notrace'

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

  parent reply	other threads:[~2016-06-21 12:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 10:57 Chunyu Hu
2016-06-21 12:22 ` kbuild test robot
2016-06-21 12:39 ` kbuild test robot [this message]
2016-06-22  5:33   ` Chunyu Hu
2016-06-22 13:08 ` Steven Rostedt
2016-06-23 14:20   ` Chunyu Hu
2016-06-23 14:39     ` Steven Rostedt
2016-06-23 14:58       ` Chunyu Hu
2016-06-23 15:11         ` Steven Rostedt

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=201606212034.rXT4171b%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=chuhu@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®