From: Oleg Nesterov <oleg@redhat.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Sasha Levin <sasha.levin@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Jiri Slaby <jslaby@suse.cz>
Subject: Re: [sashal-linux-stable-security:linux-3.12.y-security 590/1388] mm/util.c:277:3: error: implicit declaration of function 'for_each_thread'
Date: Thu, 8 Sep 2016 14:26:51 +0200 [thread overview]
Message-ID: <20160908122650.GB15874@redhat.com> (raw)
In-Reply-To: <201609080220.fropEFaF%fengguang.wu@intel.com>
On 09/08, kbuild test robot wrote:
>
> Hi Oleg,
>
> FYI, the error/warning still remains.
I guess this is because you need to backport for_each_thread first ;)
And probably a couple more commits before this one.
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable-security.git linux-3.12.y-security
> head: aac46739e3b30a5e6a0ccb2820dfde1333e9f24b
> commit: 9ac1e8708f42427bffe12c0f7f0813efe730a29d [590/1388] vm_is_stack: use for_each_thread() rather then buggy while_each_thread()
> config: i386-randconfig-s1-201636 (attached as .config)
> compiler: gcc-4.9 (Debian 4.9.3-14) 4.9.3
> reproduce:
> git checkout 9ac1e8708f42427bffe12c0f7f0813efe730a29d
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All errors (new ones prefixed by >>):
>
> mm/util.c: In function 'vm_is_stack':
> >> mm/util.c:277:3: error: implicit declaration of function 'for_each_thread' [-Werror=implicit-function-declaration]
> for_each_thread(task, t) {
> ^
> >> mm/util.c:277:28: error: expected ';' before '{' token
> for_each_thread(task, t) {
> ^
> cc1: some warnings being treated as errors
>
> vim +/for_each_thread +277 mm/util.c
>
> 271 return task->pid;
> 272
> 273 if (in_group) {
> 274 struct task_struct *t;
> 275
> 276 rcu_read_lock();
> > 277 for_each_thread(task, t) {
> 278 if (vm_is_stack_for_task(t, vma)) {
> 279 ret = t->pid;
> 280 goto done;
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-09-08 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 18:05 [sashal-linux-stable-security:linux-3.12.y-security 590/1388] mm/util.c:277:3: error: implicit declaration of function 'for_each_thread' kbuild test robot
2016-09-08 12:26 ` Oleg Nesterov [this message]
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=20160908122650.GB15874@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=jslaby@suse.cz \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=sasha.levin@oracle.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 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.