From: Hoeun Ryu <hoeun.ryu@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>, Ingo Molnar <mingo@kernel.org>,
Andy Lutomirski <luto@kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Oleg Nesterov <oleg@redhat.com>,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com
Subject: Re: [PATCH v5] fork: free vmapped stacks in cache when cpus are offline
Date: Sun, 12 Feb 2017 10:44:43 +0900 [thread overview]
Message-ID: <176AF453-1CEF-4AF3-8A5F-B8AFE16A16CD@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1702112118120.3734@nanos>
> On Feb 12, 2017, at 5:19 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
>
>> On Sat, 11 Feb 2017, kbuild test robot wrote:
>>
>> Hi Hoeun,
>>
>> [auto build test ERROR on linus/master]
>> [also build test ERROR on v4.10-rc7 next-20170210]
>> [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/Hoeun-Ryu/fork-free-vmapped-stacks-in-cache-when-cpus-are-offline/20170211-183401
>> config: ia64-allmodconfig (attached as .config)
>> compiler: ia64-linux-gcc (GCC) 6.2.0
>> 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=ia64
>>
>> All errors (new ones prefixed by >>):
>>
>> kernel/fork.c: In function 'fork_init':
>>>> kernel/fork.c:483:2: error: implicit declaration of function 'vm_stack_cache_init' [-Werror=implicit-function-declaration]
>> vm_stack_cache_init();
>> ^~~~~~~~~~~~~~~~~~~
>
> Right. This needs to move to a different place as that part is nested inside
>
> #ifndef CONFIG_ARCH_THREAD_STACK_ALLOCATOR
>
> That's an horrible ifdef maze in that file.
>
I think we should rollback to v4. Do you agree?
> Thanks,
>
> tglx
next prev parent reply other threads:[~2017-02-12 1:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 10:26 Hoeun Ryu
2017-02-11 11:18 ` kbuild test robot
2017-02-11 20:19 ` Thomas Gleixner
2017-02-12 1:44 ` Hoeun Ryu [this message]
2017-02-12 12:19 ` Thomas Gleixner
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=176AF453-1CEF-4AF3-8A5F-B8AFE16A16CD@gmail.com \
--to=hoeun.ryu@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=tglx@linutronix.de \
/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®