From: kbuild test robot <lkp@intel.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: kbuild-all@01.org, Alexander Potapenko <glider@google.com>,
Andrey Konovalov <adech.fo@gmail.com>,
Dmitriy Vyukov <dvyukov@google.com>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
will.deacon@arm.com, catalin.marinas@arm.com,
Andrew Morton <akpm@linux-foundation.org>,
kasan-dev@googlegroups.com, LKML <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] sched/kasan: clear stale stack poison
Date: Wed, 2 Mar 2016 04:05:48 +0800 [thread overview]
Message-ID: <201603020407.MpuzPX1T%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160301194204.GB335@leverpostej>
[-- Attachment #1: Type: text/plain, Size: 2606 bytes --]
Hi Mark,
[auto build test WARNING on tip/sched/core]
[also build test WARNING on v4.5-rc6 next-20160301]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Mark-Rutland/sched-kasan-clear-stale-stack-poison/20160302-034556
config: sparc64-allyesconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=sparc64
All warnings (new ones prefixed by >>):
In file included from kernel/sched/core.c:29:0:
include/linux/kasan.h:71:53: warning: 'struct task_struct' declared inside parameter list
static inline void kasan_unpoison_task_stack(struct task_struct *idle) {}
^
include/linux/kasan.h:71:53: warning: its scope is only this definition or declaration, which is probably not what you want
kernel/sched/core.c: In function 'init_idle':
>> kernel/sched/core.c:5026:2: warning: passing argument 1 of 'kasan_unpoison_task_stack' from incompatible pointer type
kasan_unpoison_task_stack(idle);
^
In file included from kernel/sched/core.c:29:0:
include/linux/kasan.h:71:20: note: expected 'struct task_struct *' but argument is of type 'struct task_struct *'
static inline void kasan_unpoison_task_stack(struct task_struct *idle) {}
^
vim +/kasan_unpoison_task_stack +5026 kernel/sched/core.c
5010 *
5011 * NOTE: this function does not set the idle thread's NEED_RESCHED
5012 * flag, to make booting more robust.
5013 */
5014 void init_idle(struct task_struct *idle, int cpu)
5015 {
5016 struct rq *rq = cpu_rq(cpu);
5017 unsigned long flags;
5018
5019 raw_spin_lock_irqsave(&idle->pi_lock, flags);
5020 raw_spin_lock(&rq->lock);
5021
5022 __sched_fork(0, idle);
5023 idle->state = TASK_RUNNING;
5024 idle->se.exec_start = sched_clock();
5025
> 5026 kasan_unpoison_task_stack(idle);
5027
5028 #ifdef CONFIG_SMP
5029 /*
5030 * Its possible that init_idle() gets called multiple times on a task,
5031 * in that case do_set_cpus_allowed() will not do the right thing.
5032 *
5033 * And since this is boot we can forgo the serialization.
5034 */
---
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: 45097 bytes --]
next prev parent reply other threads:[~2016-03-01 20:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 12:38 [PATCH v1] kasan, arm64: Unpoison dirty stack frames when resuming from suspend Alexander Potapenko
2016-02-26 13:53 ` Mark Rutland
2016-02-26 17:28 ` Alexander Potapenko
2016-03-01 19:37 ` Mark Rutland
2016-03-01 19:42 ` Mark Rutland
2016-03-01 20:05 ` kbuild test robot [this message]
2016-03-02 12:53 ` Andrey Ryabinin
2016-03-02 13:51 ` [PATCH 1/2] cpu, idle: move init_idle() out of idle_thread_get() Andrey Ryabinin
2016-03-02 13:51 ` [PATCH 2/2] kasan: unpoison stack of idle task on cpu online Andrey Ryabinin
2016-03-02 14:50 ` Mark Rutland
2016-03-02 15:27 ` Andrey Ryabinin
2016-03-02 15:43 ` Mark Rutland
2016-02-27 1:05 ` [PATCH v1] kasan, arm64: Unpoison dirty stack frames when resuming from suspend 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=201603020407.MpuzPX1T%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=adech.fo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ryabinin.a.a@gmail.com \
--cc=will.deacon@arm.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).