mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Michael Sartain <mikesart@fastmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Joel Fernandes <joelaf@google.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] tracing: Add saved_tgids file to show cached pid to tgid mappings
Date: Sun, 2 Jul 2017 09:47:20 +0800	[thread overview]
Message-ID: <201707020917.Y7B1ppWj%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170630171748.sf5rnjb7pyws6ewu@mikesart-cos>

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

Hi Michael,

[auto build test ERROR on trace/for-next]
[also build test ERROR on next-20170630]
[cannot apply to tip/perf/core linus/master v4.12-rc7]
[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/Michael-Sartain/tracing-Add-saved_tgids-file-to-show-cached-pid-to-tgid-mappings/20170702-092448
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git for-next
config: i386-randconfig-x070-07010433 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   kernel//trace/trace.c: In function 'saved_cmdlines_next':
>> kernel//trace/trace.c:4612:22: error: implicit declaration of function 'trace_find_tgid' [-Werror=implicit-function-declaration]
      if (tgid_check && !trace_find_tgid(*ptr))
                         ^~~~~~~~~~~~~~~
   kernel//trace/trace.c: In function 'saved_cmdlines_start':
>> kernel//trace/trace.c:4627:21: error: 'tgid_map' undeclared (first use in this function)
     if (tgid_check && !tgid_map)
                        ^~~~~~~~
   kernel//trace/trace.c:4627:21: note: each undeclared identifier is reported only once for each function it appears in
   cc1: some warnings being treated as errors

vim +/trace_find_tgid +4612 kernel//trace/trace.c

  4606		(*pos)++;
  4607	
  4608		for (; ptr < &savedcmd->map_cmdline_to_pid[savedcmd->cmdline_num];
  4609		     ptr++) {
  4610			if (*ptr == -1 || *ptr == NO_CMDLINE_MAP)
  4611				continue;
> 4612			if (tgid_check && !trace_find_tgid(*ptr))
  4613				continue;
  4614	
  4615			return ptr;
  4616		}
  4617	
  4618		return NULL;
  4619	}
  4620	
  4621	static void *saved_cmdlines_start(struct seq_file *m, loff_t *pos)
  4622	{
  4623		void *v;
  4624		loff_t l = 0;
  4625		long tgid_check = (long) m->private;
  4626	
> 4627		if (tgid_check && !tgid_map)
  4628			return NULL;
  4629	
  4630		preempt_disable();

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

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

  parent reply	other threads:[~2017-07-02  1:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-30 17:17 Michael Sartain
2017-06-30 21:50 ` Steven Rostedt
2017-06-30 23:37   ` Joel Fernandes
2017-07-01  0:32   ` Michael Sartain
2017-07-02  1:47 ` kbuild test robot [this message]
2017-07-02  2:03 ` kbuild test robot

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=201707020917.Y7B1ppWj%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=joelaf@google.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikesart@fastmail.com \
    --cc=mingo@redhat.com \
    --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®