linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Serge E. Hallyn" <serge@hallyn.com>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-security-module@vger.kernel.org,
	Paul Moore <paul@paul-moore.com>,
	Ryan Foster <foster.ryan.r@gmail.com>,
	Christian Brauner <brauner@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] Clarify the rootid_owns_currentns
Date: Sat, 15 Nov 2025 07:16:03 +0800	[thread overview]
Message-ID: <202511150644.EXaXOsVc-lkp@intel.com> (raw)
In-Reply-To: <aRegH8P4cPlzzlX9@mail.hallyn.com>

Hi Serge,

kernel test robot noticed the following build warnings:

[auto build test WARNING on linus/master]
[also build test WARNING on brauner-vfs/vfs.all v6.18-rc5 next-20251114]
[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/Serge-E-Hallyn/Clarify-the-rootid_owns_currentns/20251115-053655
base:   linus/master
patch link:    https://lore.kernel.org/r/aRegH8P4cPlzzlX9%40mail.hallyn.com
patch subject: [PATCH] Clarify the rootid_owns_currentns
config: alpha-allnoconfig (https://download.01.org/0day-ci/archive/20251115/202511150644.EXaXOsVc-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251115/202511150644.EXaXOsVc-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/202511150644.EXaXOsVc-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> Warning: security/commoncap.c:369 function parameter 'kuid' not described in 'kuid_root_in_ns'
>> Warning: security/commoncap.c:369 function parameter 'ns' not described in 'kuid_root_in_ns'

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2025-11-14 23:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 21:33 [PATCH] Clarify the rootid_owns_currentns Serge E. Hallyn
2025-11-14 23:16 ` kernel test robot [this message]
2025-11-18 14:16 ` Serge E. Hallyn
2025-11-18 15:47   ` Paul Moore
2025-11-18 23:59     ` Serge E. Hallyn
2025-11-19  0:05     ` Serge E. Hallyn
2025-11-19  0:29       ` Paul Moore

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=202511150644.EXaXOsVc-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=brauner@kernel.org \
    --cc=foster.ryan.r@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=paul@paul-moore.com \
    --cc=serge@hallyn.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;
as well as URLs for NNTP newsgroup(s).