Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH] security: Allow dropping bounding set process-wide
Date: Mon, 28 Sep 2026 13:22:44 +0800	[thread overview]
Message-ID: <202609281347.3heKlnv9-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: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260928/202609281347.3heKlnv9-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260928/202609281347.3heKlnv9-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/202609281347.3heKlnv9-lkp@intel.com/

All errors (new ones prefixed by >>):

>> security/commoncap.c:1399:22: error: call to undeclared function 'mk_kernel_cap'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
    1399 |         kernel_cap_t mask = mk_kernel_cap((u32)low, (u32)high);
         |                             ^
>> security/commoncap.c:1399:15: error: initializing 'kernel_cap_t' with an expression of incompatible type 'int'
    1399 |         kernel_cap_t mask = mk_kernel_cap((u32)low, (u32)high);
         |                      ^      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   2 errors generated.


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

           reply	other threads:[~2026-09-28  5:23 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20260922095816.1191799-1-ruanjinjie@huawei.com>]

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=202609281347.3heKlnv9-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox