All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: lkp@lists.01.org
Subject: Re: [PATCH] kthread: to_live_kthread() needs try_get_task_stack()
Date: Wed, 29 Jun 2016 20:44:27 +0200	[thread overview]
Message-ID: <20160629184427.GA3928@redhat.com> (raw)
In-Reply-To: <201606300245.vASQFf80%fengguang.wu@intel.com>

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

On 06/30, kbuild test robot wrote:
>
> Hi,
>
> [auto build test ERROR on linus/master]
> [also build test ERROR on v4.7-rc5 next-20160629]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

Yes, please ignore this, the patch is based on Andy's x86/vmap_stack
tree.


> url:    https://github.com/0day-ci/linux/commits/Oleg-Nesterov/kthread-to_live_kthread-needs-try_get_task_stack/20160630-020824
> config: i386-tinyconfig (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/kthread.c: In function 'to_live_kthread':
> >> kernel/kthread.c:67:23: error: implicit declaration of function 'try_get_task_stack' [-Werror=implicit-function-declaration]
>      if (likely(vfork) && try_get_task_stack(k))
>                           ^~~~~~~~~~~~~~~~~~
>    kernel/kthread.c: In function 'kthread_unpark':
> >> kernel/kthread.c:430:3: error: implicit declaration of function 'put_task_stack' [-Werror=implicit-function-declaration]
>       put_task_stack(k);
>       ^~~~~~~~~~~~~~
>    cc1: some warnings being treated as errors
> 
> vim +/try_get_task_stack +67 kernel/kthread.c
> 
>     61		return __to_kthread(k->vfork_done);
>     62	}
>     63	
>     64	static struct kthread *to_live_kthread(struct task_struct *k)
>     65	{
>     66		struct completion *vfork = ACCESS_ONCE(k->vfork_done);
>   > 67		if (likely(vfork) && try_get_task_stack(k))
>     68			return __to_kthread(vfork);
>     69		return NULL;
>     70	}
> 
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation




WARNING: multiple messages have this Message-ID (diff)
From: Oleg Nesterov <oleg@redhat.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Andy Lutomirski <luto@amacapital.net>,
	Andy Lutomirski <luto@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>, Tejun Heo <tj@kernel.org>,
	LKP <lkp@01.org>, LKML <linux-kernel@vger.kernel.org>,
	kernel test robot <xiaolong.ye@intel.com>
Subject: Re: [PATCH] kthread: to_live_kthread() needs try_get_task_stack()
Date: Wed, 29 Jun 2016 20:44:27 +0200	[thread overview]
Message-ID: <20160629184427.GA3928@redhat.com> (raw)
In-Reply-To: <201606300245.vASQFf80%fengguang.wu@intel.com>

On 06/30, kbuild test robot wrote:
>
> Hi,
>
> [auto build test ERROR on linus/master]
> [also build test ERROR on v4.7-rc5 next-20160629]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

Yes, please ignore this, the patch is based on Andy's x86/vmap_stack
tree.


> url:    https://github.com/0day-ci/linux/commits/Oleg-Nesterov/kthread-to_live_kthread-needs-try_get_task_stack/20160630-020824
> config: i386-tinyconfig (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/kthread.c: In function 'to_live_kthread':
> >> kernel/kthread.c:67:23: error: implicit declaration of function 'try_get_task_stack' [-Werror=implicit-function-declaration]
>      if (likely(vfork) && try_get_task_stack(k))
>                           ^~~~~~~~~~~~~~~~~~
>    kernel/kthread.c: In function 'kthread_unpark':
> >> kernel/kthread.c:430:3: error: implicit declaration of function 'put_task_stack' [-Werror=implicit-function-declaration]
>       put_task_stack(k);
>       ^~~~~~~~~~~~~~
>    cc1: some warnings being treated as errors
> 
> vim +/try_get_task_stack +67 kernel/kthread.c
> 
>     61		return __to_kthread(k->vfork_done);
>     62	}
>     63	
>     64	static struct kthread *to_live_kthread(struct task_struct *k)
>     65	{
>     66		struct completion *vfork = ACCESS_ONCE(k->vfork_done);
>   > 67		if (likely(vfork) && try_get_task_stack(k))
>     68			return __to_kthread(vfork);
>     69		return NULL;
>     70	}
> 
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

  reply	other threads:[~2016-06-29 18:44 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27  5:22 kthread_stop insanity (Re: [[DEBUG] force] 2642458962: BUG: unable to handle kernel paging request at ffffc90000997f18) Andy Lutomirski
2016-06-27  5:22 ` Andy Lutomirski
2016-06-27  8:28 ` Peter Zijlstra
2016-06-27  8:28   ` Peter Zijlstra
2016-06-27 14:54 ` Oleg Nesterov
2016-06-27 14:54   ` Oleg Nesterov
2016-06-27 15:44   ` Andy Lutomirski
2016-06-27 15:44     ` Andy Lutomirski
2016-06-27 17:00     ` Oleg Nesterov
2016-06-27 17:00       ` Oleg Nesterov
2016-06-28 18:58       ` Oleg Nesterov
2016-06-28 18:58         ` Oleg Nesterov
2016-06-28 19:12         ` Andy Lutomirski
2016-06-28 19:12           ` Andy Lutomirski
2016-06-28 20:12           ` Oleg Nesterov
2016-06-28 20:12             ` Oleg Nesterov
2016-06-28 20:54             ` Andy Lutomirski
2016-06-28 20:54               ` Andy Lutomirski
2016-06-28 21:14               ` Linus Torvalds
2016-06-28 21:14                 ` Linus Torvalds
2016-06-28 21:18                 ` Linus Torvalds
2016-06-28 21:18                   ` Linus Torvalds
2016-06-28 21:21                 ` Andy Lutomirski
2016-06-28 21:21                   ` Andy Lutomirski
2016-06-28 21:35                   ` Linus Torvalds
2016-06-28 21:35                     ` Linus Torvalds
2016-06-28 21:40                     ` Linus Torvalds
2016-06-28 21:40                       ` Linus Torvalds
2016-06-28 22:47                       ` Oleg Nesterov
2016-06-28 22:47                         ` Oleg Nesterov
2016-06-28 22:59               ` Oleg Nesterov
2016-06-28 22:59                 ` Oleg Nesterov
2016-06-29 15:34                 ` Andy Lutomirski
2016-06-29 15:34                   ` Andy Lutomirski
2016-06-29 18:03                   ` [PATCH] kthread: to_live_kthread() needs try_get_task_stack() Oleg Nesterov
2016-06-29 18:03                     ` Oleg Nesterov
2016-06-29 18:28                     ` kbuild test robot
2016-06-29 18:28                       ` kbuild test robot
2016-06-29 18:44                       ` Oleg Nesterov [this message]
2016-06-29 18:44                         ` Oleg Nesterov
2016-06-29 18:51                     ` kbuild test robot
2016-06-29 18:51                       ` kbuild test robot
2016-06-29 23:01                     ` Andy Lutomirski
2016-06-29 23:01                       ` Andy Lutomirski
2016-06-29 23:33         ` kthread_stop insanity (Re: [[DEBUG] force] 2642458962: BUG: unable to handle kernel paging request at ffffc90000997f18) Andy Lutomirski
2016-06-29 23:33           ` Andy Lutomirski
2016-06-27 17:16 ` Linus Torvalds
2016-06-27 17:16   ` Linus Torvalds

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=20160629184427.GA3928@redhat.com \
    --to=oleg@redhat.com \
    --cc=lkp@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.