From: kernel test robot <lkp@intel.com>
To: Ryan Foster <foster.ryan.r@gmail.com>, selinux@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, serge@hallyn.com,
paul@paul-moore.com, Ryan Foster <foster.ryan.r@gmail.com>
Subject: Re: [PATCH] security: Add KUnit tests for rootid_owns_currentns()
Date: Tue, 11 Nov 2025 14:52:54 +0800 [thread overview]
Message-ID: <202511111459.1ToyUP5p-lkp@intel.com> (raw)
In-Reply-To: <20251110143748.4144288-1-foster.ryan.r@gmail.com>
Hi Ryan,
kernel test robot noticed the following build errors:
[auto build test ERROR on pcmoore-selinux/next]
[also build test ERROR on linus/master v6.18-rc5 next-20251110]
[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/Ryan-Foster/security-Add-KUnit-tests-for-rootid_owns_currentns/20251110-223824
base: https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git next
patch link: https://lore.kernel.org/r/20251110143748.4144288-1-foster.ryan.r%40gmail.com
patch subject: [PATCH] security: Add KUnit tests for rootid_owns_currentns()
config: mips-randconfig-r053-20251111 (https://download.01.org/0day-ci/archive/20251111/202511111459.1ToyUP5p-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251111/202511111459.1ToyUP5p-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/202511111459.1ToyUP5p-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
>> security/commoncap_test.c:23:3: error: conflicting types for 'vfsuid_t'
} vfsuid_t;
^~~~~~~~
In file included from include/linux/fs.h:45,
from arch/mips/include/asm/elf.h:12,
from include/linux/elf.h:6,
from include/linux/module.h:20,
from include/kunit/test.h:24,
from security/commoncap_test.c:9:
include/linux/mnt_idmapping.h:17:3: note: previous declaration of 'vfsuid_t' was here
} vfsuid_t;
^~~~~~~~
>> security/commoncap_test.c:26:21: error: conflicting types for '__vfsuid_val'
static inline uid_t __vfsuid_val(vfsuid_t uid)
^~~~~~~~~~~~
In file included from include/linux/fs.h:45,
from arch/mips/include/asm/elf.h:12,
from include/linux/elf.h:6,
from include/linux/module.h:20,
from include/kunit/test.h:24,
from security/commoncap_test.c:9:
include/linux/mnt_idmapping.h:34:21: note: previous definition of '__vfsuid_val' was here
static inline uid_t __vfsuid_val(vfsuid_t uid)
^~~~~~~~~~~~
>> security/commoncap_test.c:31: warning: "VFSUIDT_INIT" redefined
#define VFSUIDT_INIT(val) ((vfsuid_t){ __kuid_val(val) })
In file included from include/linux/fs.h:45,
from arch/mips/include/asm/elf.h:12,
from include/linux/elf.h:6,
from include/linux/module.h:20,
from include/kunit/test.h:24,
from security/commoncap_test.c:9:
include/linux/mnt_idmapping.h:109: note: this is the location of the previous definition
#define VFSUIDT_INIT(val) (vfsuid_t){ __kuid_val(val) }
vim +/vfsuid_t +23 security/commoncap_test.c
18
19 /* Forward declare the minimal types we need - match the actual kernel definitions */
20 struct mnt_idmap;
21 typedef struct {
22 uid_t val;
> 23 } vfsuid_t;
24
25 /* Minimal macros we need - match kernel definitions from mnt_idmapping.h */
> 26 static inline uid_t __vfsuid_val(vfsuid_t uid)
27 {
28 return uid.val;
29 }
30
> 31 #define VFSUIDT_INIT(val) ((vfsuid_t){ __kuid_val(val) })
32 #define INVALID_VFSUID VFSUIDT_INIT(INVALID_UID)
33
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-11-11 6:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 14:37 [PATCH] security: Add KUnit tests for rootid_owns_currentns() Ryan Foster
2025-11-11 0:33 ` Serge E. Hallyn
2025-11-11 6:52 ` kernel test robot [this message]
2025-11-11 7:03 ` kernel test robot
2025-11-21 17:48 ` [PATCH v2] security: Rename functions and add namespace mapping tests Ryan Foster
2025-11-25 15:15 ` Serge E. Hallyn
2025-12-04 21:56 ` [PATCH] security: Add KUnit tests for kuid_root_in_ns and vfsuid_root_in_currentns Ryan Foster
2025-12-16 22:57 ` Paul Moore
2025-12-18 18:49 ` [PATCH v3 sec cap tests] " Ryan Foster
2025-12-28 19:45 ` commoncap KUnit tests v4 Ryan Foster
2025-12-28 19:45 ` [PATCH v4] security: Add KUnit tests for kuid_root_in_ns and vfsuid_root_in_currentns Ryan Foster
2025-12-29 4:14 ` Serge E. Hallyn
2025-12-29 14:23 ` [PATCH v5] " Ryan Foster
2025-12-29 13:56 ` [PATCH v4] " kernel test robot
2025-12-29 18:35 ` kernel test robot
2025-12-30 15:13 ` [PATCH v5] " Ryan Foster
2026-01-06 21:07 ` Serge E. Hallyn
2026-01-07 21:51 ` [PATCH v6] " Ryan Foster
2026-01-10 4:50 ` Serge E. Hallyn
-- strict thread matches above, loose matches on Subject: below --
2025-11-10 1:16 [PATCH] security: Add KUnit tests for rootid_owns_currentns() ryan foster
2025-11-10 1:13 ryan foster
2025-11-10 23:17 ` Paul Moore
2025-11-11 0:12 ` 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=202511111459.1ToyUP5p-lkp@intel.com \
--to=lkp@intel.com \
--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=selinux@vger.kernel.org \
--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 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.