From: kernel test robot <lkp@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: kernel/user_namespace.c:239: warning: Function parameter or member 'map_up' not described in 'idmap_key'
Date: Tue, 17 Oct 2023 20:25:41 +0800 [thread overview]
Message-ID: <202310172019.KFiYMz7T-lkp@intel.com> (raw)
Hi Randy,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 213f891525c222e8ed145ce1ce7ae1f47921cb9c
commit: e227db4d4f125efb1cae2f1337da85bc10b3185e userns: fix a struct's kernel-doc notation
date: 9 months ago
config: x86_64-buildonly-randconfig-001-20231012 (https://download.01.org/0day-ci/archive/20231017/202310172019.KFiYMz7T-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/20231017/202310172019.KFiYMz7T-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/202310172019.KFiYMz7T-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/user_namespace.c:239: warning: Function parameter or member 'map_up' not described in 'idmap_key'
>> kernel/user_namespace.c:239: warning: Function parameter or member 'id' not described in 'idmap_key'
>> kernel/user_namespace.c:239: warning: Function parameter or member 'count' not described in 'idmap_key'
kernel/user_namespace.c:246: warning: Function parameter or member 'k' not described in 'cmp_map_id'
kernel/user_namespace.c:246: warning: Function parameter or member 'e' not described in 'cmp_map_id'
kernel/user_namespace.c:277: warning: Function parameter or member 'extents' not described in 'map_id_range_down_max'
kernel/user_namespace.c:277: warning: Function parameter or member 'map' not described in 'map_id_range_down_max'
kernel/user_namespace.c:277: warning: Function parameter or member 'id' not described in 'map_id_range_down_max'
kernel/user_namespace.c:277: warning: Function parameter or member 'count' not described in 'map_id_range_down_max'
kernel/user_namespace.c:295: warning: Function parameter or member 'extents' not described in 'map_id_range_down_base'
kernel/user_namespace.c:295: warning: Function parameter or member 'map' not described in 'map_id_range_down_base'
kernel/user_namespace.c:295: warning: Function parameter or member 'id' not described in 'map_id_range_down_base'
kernel/user_namespace.c:295: warning: Function parameter or member 'count' not described in 'map_id_range_down_base'
kernel/user_namespace.c:344: warning: Function parameter or member 'extents' not described in 'map_id_up_base'
kernel/user_namespace.c:344: warning: Function parameter or member 'map' not described in 'map_id_up_base'
kernel/user_namespace.c:344: warning: Function parameter or member 'id' not described in 'map_id_up_base'
kernel/user_namespace.c:364: warning: Function parameter or member 'extents' not described in 'map_id_up_max'
kernel/user_namespace.c:364: warning: Function parameter or member 'map' not described in 'map_id_up_max'
kernel/user_namespace.c:364: warning: Function parameter or member 'id' not described in 'map_id_up_max'
kernel/user_namespace.c:776: warning: Function parameter or member 'map' not described in 'insert_extent'
kernel/user_namespace.c:776: warning: Function parameter or member 'extent' not described in 'insert_extent'
kernel/user_namespace.c:844: warning: Function parameter or member 'map' not described in 'sort_idmaps'
vim +239 kernel/user_namespace.c
5c1469de7545a35 Eric W. Biederman 2010-06-13 230
6397fac4915ab30 Christian Brauner 2017-10-25 231 /**
e227db4d4f125ef Randy Dunlap 2023-01-07 232 * struct idmap_key - holds the information necessary to find an idmapping in a
6397fac4915ab30 Christian Brauner 2017-10-25 233 * sorted idmap array. It is passed to cmp_map_id() as first argument.
6397fac4915ab30 Christian Brauner 2017-10-25 234 */
6397fac4915ab30 Christian Brauner 2017-10-25 235 struct idmap_key {
6397fac4915ab30 Christian Brauner 2017-10-25 236 bool map_up; /* true -> id from kid; false -> kid from id */
6397fac4915ab30 Christian Brauner 2017-10-25 237 u32 id; /* id to find */
6397fac4915ab30 Christian Brauner 2017-10-25 238 u32 count; /* == 0 unless used with map_id_range_down() */
6397fac4915ab30 Christian Brauner 2017-10-25 @239 };
6397fac4915ab30 Christian Brauner 2017-10-25 240
:::::: The code at line 239 was first introduced by commit
:::::: 6397fac4915ab3002dc15aae751455da1a852f25 userns: bump idmap limits to 340
:::::: TO: Christian Brauner <christian.brauner@ubuntu.com>
:::::: CC: Eric W. Biederman <ebiederm@xmission.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-10-17 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 12:25 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-17 12:56 kernel test robot
2023-08-29 5:13 ` Randy Dunlap
2023-08-30 8:24 ` Christian Brauner
2023-10-26 5:25 ` Randy Dunlap
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=202310172019.KFiYMz7T-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rdunlap@infradead.org \
/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