mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Hoeun Ryu <hoeun.ryu@gmail.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.com>, Ingo Molnar <mingo@kernel.org>,
	Andy Lutomirski <luto@kernel.org>,
	Kees Cook <keescook@chromium.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Mateusz Guzik <mguzik@redhat.com>,
	linux-kernel@vger.kernel.org,
	kernel-hardening@lists.openwall.com,
	Hoeun Ryu <hoeun.ryu@gmail.com>
Subject: Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped stacks using cpuhp
Date: Sat, 4 Feb 2017 00:04:10 +0800	[thread overview]
Message-ID: <201702040007.vDgc4VnF%fengguang.wu@intel.com> (raw)
In-Reply-To: <1486135892-27249-1-git-send-email-hoeun.ryu@gmail.com>

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

Hi Hoeun,

[auto build test ERROR on next-20170203]
[also build test ERROR on v4.10-rc6]
[cannot apply to linus/master linux/master v4.9-rc8 v4.9-rc7 v4.9-rc6]
[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-dynamically-allocate-cache-array-for-vmapped-stacks-using-cpuhp/20170203-234431
config: i386-randconfig-x004-201705 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   kernel/fork.c: In function 'fork_init':
>> kernel/fork.c:505:6: error: 'alloc_vm_stack_cache' undeclared (first use in this function)
         alloc_vm_stack_cache, free_vm_stack_cache);
         ^~~~~~~~~~~~~~~~~~~~
   kernel/fork.c:505:6: note: each undeclared identifier is reported only once for each function it appears in
>> kernel/fork.c:505:28: error: 'free_vm_stack_cache' undeclared (first use in this function)
         alloc_vm_stack_cache, free_vm_stack_cache);
                               ^~~~~~~~~~~~~~~~~~~

vim +/alloc_vm_stack_cache +505 kernel/fork.c

   499	
   500		for (i = 0; i < UCOUNT_COUNTS; i++) {
   501			init_user_ns.ucount_max[i] = max_threads/2;
   502		}
   503	
   504		cpuhp_setup_state(CPUHP_AP_ONLINE_DYN, "vm_stack_cache",
 > 505				  alloc_vm_stack_cache, free_vm_stack_cache);
   506	}
   507	
   508	int __weak arch_dup_task_struct(struct task_struct *dst,

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

      parent reply	other threads:[~2017-02-03 16:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-03 15:30 Hoeun Ryu
2017-02-03 15:39 ` Michal Hocko
2017-02-03 16:42   ` Hoeun Ryu
2017-02-03 17:15     ` Michal Hocko
2017-02-03 17:52     ` Andy Lutomirski
2017-02-04  2:01       ` Hoeun Ryu
2017-02-05 10:18         ` Michal Hocko
2017-02-05 13:23           ` Hoeun Ryu
2017-02-03 16:04 ` kbuild test robot [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=201702040007.vDgc4VnF%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=hoeun.ryu@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mguzik@redhat.com \
    --cc=mhocko@suse.com \
    --cc=mingo@kernel.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 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®