All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [jirislaby:devel 31/31] kernel/stacktrace.c:303:34: error: 'tsk' undeclared; did you mean 'task'?
Date: Wed, 30 Oct 2019 01:55:52 +0800	[thread overview]
Message-ID: <201910300149.NeXeAWF1%lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git devel
head:   692d615834a5950b61707f688abddb56841ea5ba
commit: 692d615834a5950b61707f688abddb56841ea5ba [31/31] stacktrace: don't skip first entry on noncurrent tasks
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 7.4.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout 692d615834a5950b61707f688abddb56841ea5ba
        # save the attached .config to linux build tree
        GCC_VERSION=7.4.0 make.cross ARCH=ia64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   kernel/stacktrace.c: In function 'stack_trace_save_tsk':
>> kernel/stacktrace.c:303:34: error: 'tsk' undeclared (first use in this function); did you mean 'task'?
      .skip = skipnr + !!(current == tsk),
                                     ^~~
                                     task
   kernel/stacktrace.c:303:34: note: each undeclared identifier is reported only once for each function it appears in

vim +303 kernel/stacktrace.c

   285	
   286	/**
   287	 * stack_trace_save_tsk - Save a task stack trace into a storage array
   288	 * @task:	The task to examine
   289	 * @store:	Pointer to storage array
   290	 * @size:	Size of the storage array
   291	 * @skipnr:	Number of entries to skip at the start of the stack trace
   292	 *
   293	 * Return: Number of trace entries stored
   294	 */
   295	unsigned int stack_trace_save_tsk(struct task_struct *task,
   296					  unsigned long *store, unsigned int size,
   297					  unsigned int skipnr)
   298	{
   299		struct stack_trace trace = {
   300			.entries	= store,
   301			.max_entries	= size,
   302			/* skip this function if they are tracing us */
 > 303			.skip	= skipnr + !!(current == tsk),
   304		};
   305	
   306		save_stack_trace_tsk(task, &trace);
   307		return trace.nr_entries;
   308	}
   309	

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

                 reply	other threads:[~2019-10-29 17:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201910300149.NeXeAWF1%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.