From: kernel test robot <lkp@intel.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH] security: Allow dropping bounding set process-wide
Date: Sun, 27 Sep 2026 06:57:38 +0800 [thread overview]
Message-ID: <202609270637.Wfe1SQY8-lkp@intel.com> (raw)
In-Reply-To: <20260922095816.1191799-1-ruanjinjie@huawei.com>
Hi Jinjie,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on pcmoore-selinux/next]
[also build test ERROR on linus/master v7.3-rc4 next-20260925]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Jinjie-Ruan/security-Allow-dropping-bounding-set-process-wide/20260922-175816
base: https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git next
patch link: https://lore.kernel.org/r/20260922095816.1191799-1-ruanjinjie%40huawei.com
patch subject: [RFC PATCH] security: Allow dropping bounding set process-wide
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20260927/202609270637.Wfe1SQY8-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260927/202609270637.Wfe1SQY8-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609270637.Wfe1SQY8-lkp@intel.com/
All errors (new ones prefixed by >>):
security/commoncap.c: In function 'cap_prctl_drop_mask':
>> security/commoncap.c:1399:29: error: implicit declaration of function 'mk_kernel_cap' [-Wimplicit-function-declaration]
1399 | kernel_cap_t mask = mk_kernel_cap((u32)low, (u32)high);
| ^~~~~~~~~~~~~
>> security/commoncap.c:1399:29: error: invalid initializer
vim +/mk_kernel_cap +1399 security/commoncap.c
1396
1397 static int cap_prctl_drop_mask(unsigned long low, unsigned long high)
1398 {
> 1399 kernel_cap_t mask = mk_kernel_cap((u32)low, (u32)high);
1400
1401 if (cap_isclear(mask))
1402 return 0;
1403
1404 if (!ns_capable(current_user_ns(), CAP_SETPCAP))
1405 return -EPERM;
1406
1407 return cap_bset_drop_process(mask);
1408 }
1409
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-09-26 22:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 9:58 [RFC PATCH] security: Allow dropping bounding set process-wide Jinjie Ruan
2026-09-22 10:06 ` sashiko-bot
2026-09-22 17:01 ` Serge E. Hallyn
2026-09-23 2:10 ` Andrew G. Morgan
2026-09-24 8:46 ` Jinjie Ruan
2026-09-25 14:34 ` Serge E. Hallyn
2026-09-28 3:10 ` Jinjie Ruan
2026-09-28 13:13 ` Serge E. Hallyn
2026-09-24 8:05 ` Jinjie Ruan
2026-09-25 13:17 ` Serge E. Hallyn
2026-09-25 14:28 ` Andrew G. Morgan
2026-09-25 14:42 ` Serge E. Hallyn
2026-09-27 15:31 ` Andrew G. Morgan
2026-09-28 12:37 ` Jinjie Ruan
2026-09-28 12:34 ` Jinjie Ruan
2026-09-26 22:57 ` kernel test robot [this message]
2026-09-28 5:22 ` kernel test robot
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=202609270637.Wfe1SQY8-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ruanjinjie@huawei.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.