linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, serge@hallyn.com, ebiederm@xmission.com,
	agruenba@redhat.com, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, oleg@redhat.com,
	paul@paul-moore.com, ktkhai@virtuozzo.com,
	viro@zeniv.linux.org.uk, avagin@openvz.org,
	linux-api@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	mtk.manpages@gmail.com, akpm@linux-foundation.org,
	luto@amacapital.net, gorcunov@openvz.org, mingo@kernel.org,
	keescook@chromium.org
Subject: Re: [PATCH v4] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy
Date: Sat, 29 Apr 2017 17:17:04 +0800	[thread overview]
Message-ID: <201704291753.q3dMNEDp%fengguang.wu@intel.com> (raw)
In-Reply-To: <149338066474.18594.2768059055849440055.stgit@localhost.localdomain>

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

Hi Kirill,

[auto build test ERROR on linus/master]
[also build test ERROR on v4.11-rc8 next-20170428]
[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/Kirill-Tkhai/pid_ns-Introduce-ioctl-to-set-vector-of-ns_last_pid-s-on-ns-hierarhy/20170429-155011
config: i386-defconfig (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/pid_namespace.c: In function 'pidns_set_last_pid_vec':
>> kernel/pid_namespace.c:450:38: error: 'pid_max' undeclared (first use in this function)
      if (!top || pid[i] < 0 || pid[i] > pid_max)
                                         ^~~~~~~
   kernel/pid_namespace.c:450:38: note: each undeclared identifier is reported only once for each function it appears in

vim +/pid_max +450 kernel/pid_namespace.c

   444		if (copy_from_user(pid, &vec->pid[0], nr * sizeof(pid_t)) != 0)
   445			return -EFAULT;
   446	
   447		top = pid_ns;
   448		for (i = 0; i < nr-1; i++) {
   449			top = top->parent;
 > 450			if (!top || pid[i] < 0 || pid[i] > pid_max)
   451				return -EINVAL;
   452		}
   453		if (!ns_capable(top->user_ns, CAP_SYS_ADMIN))

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

      reply	other threads:[~2017-04-29  9:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28 11:58 [PATCH v4] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy Kirill Tkhai
2017-04-29  9:17 ` 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=201704291753.q3dMNEDp%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=agruenba@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=avagin@openvz.org \
    --cc=ebiederm@xmission.com \
    --cc=gorcunov@openvz.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@01.org \
    --cc=keescook@chromium.org \
    --cc=ktkhai@virtuozzo.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=oleg@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=serge@hallyn.com \
    --cc=viro@zeniv.linux.org.uk \
    /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).