From: kernel test robot <lkp@intel.com>
To: Chen Ridong <chenridong@huaweicloud.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC next v2 5/5] ucount: add rlimit cache for ucount
Date: Sat, 10 May 2025 03:10:50 +0800 [thread overview]
Message-ID: <202505100258.uXDFTc4e-lkp@intel.com> (raw)
In-Reply-To: <20250509072054.148257-6-chenridong@huaweicloud.com>
Hi Chen,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20250508]
url: https://github.com/intel-lab-lkp/linux/commits/Chen-Ridong/user_namespace-add-children-list-node/20250509-153709
base: next-20250508
patch link: https://lore.kernel.org/r/20250509072054.148257-6-chenridong%40huaweicloud.com
patch subject: [RFC next v2 5/5] ucount: add rlimit cache for ucount
config: i386-buildonly-randconfig-004-20250510 (https://download.01.org/0day-ci/archive/20250510/202505100258.uXDFTc4e-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250510/202505100258.uXDFTc4e-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/202505100258.uXDFTc4e-lkp@intel.com/
All errors (new ones prefixed by >>):
ld: kernel/ucount.o: in function `rlimit_drain_type_cache':
>> ucount.c:(.text+0x417): undefined reference to `ns_next_child_pre'
>> ld: ucount.c:(.text+0x48a): undefined reference to `ns_next_child_pre'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-05-09 19:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 7:20 [RFC next v2 0/5] ucount: add rlimit cache for ucount Chen Ridong
2025-05-09 7:20 ` [RFC next v2 1/5] user_namespace: add children list node Chen Ridong
2025-05-09 7:20 ` [RFC next v2 2/5] usernamespace: make usernamespace rcu safe Chen Ridong
2025-05-09 7:20 ` [RFC next v2 3/5] user_namespace: add user_ns iteration helper Chen Ridong
2025-05-09 7:20 ` [RFC next v2 4/5] uounts: factor out __inc_rlimit_get_ucounts/__dec_rlimit_put_ucounts Chen Ridong
2025-05-09 7:20 ` [RFC next v2 5/5] ucount: add rlimit cache for ucount Chen Ridong
2025-05-09 19:10 ` kernel test robot [this message]
2025-05-09 20:18 ` [RFC next v2 0/5] " Andrew Morton
2025-05-12 10:48 ` Sebastian Andrzej Siewior
2025-05-13 1:48 ` Chen Ridong
2025-05-15 10:29 ` Christian Brauner
2025-05-15 12:04 ` Chen Ridong
2025-05-16 11:48 ` Alexey Gladkov
2025-05-19 13:39 ` Chen Ridong
2025-05-19 16:32 ` Alexey Gladkov
2025-05-21 1:32 ` Chen Ridong
2025-05-21 7:29 ` Alexey Gladkov
2025-05-22 22:48 ` Andrei Vagin
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=202505100258.uXDFTc4e-lkp@intel.com \
--to=lkp@intel.com \
--cc=chenridong@huaweicloud.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.