From: kernel test robot <lkp@intel.com>
To: NeilBrown <neilb@ownmail.net>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
Amir Goldstein <amir73il@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 5/6] VFS/audit: introduce kern_path_parent() for audit
Date: Sun, 7 Sep 2025 10:17:00 +0800 [thread overview]
Message-ID: <202509070916.8uBFTDCH-lkp@intel.com> (raw)
In-Reply-To: <20250906050015.3158851-6-neilb@ownmail.net>
Hi NeilBrown,
kernel test robot noticed the following build warnings:
[auto build test WARNING on brauner-vfs/vfs.all]
[also build test WARNING on pcmoore-audit/next viro-vfs/for-next linus/master v6.17-rc4 next-20250905]
[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/NeilBrown/fs-proc-Don-t-look-root-inode-when-creating-self-and-thread-self/20250906-130248
base: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
patch link: https://lore.kernel.org/r/20250906050015.3158851-6-neilb%40ownmail.net
patch subject: [PATCH 5/6] VFS/audit: introduce kern_path_parent() for audit
config: x86_64-buildonly-randconfig-001-20250907 (https://download.01.org/0day-ci/archive/20250907/202509070916.8uBFTDCH-lkp@intel.com/config)
compiler: gcc-13 (Debian 13.3.0-16) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250907/202509070916.8uBFTDCH-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/202509070916.8uBFTDCH-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: fs/namei.c:2804 function parameter 'path' not described in 'kern_path_parent'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-09-07 2:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-06 4:57 [PATCH 0/6] VFS: more prep for change to directory locking NeilBrown
2025-09-06 4:57 ` [PATCH 1/6] fs/proc: Don't look root inode when creating "self" and "thread-self" NeilBrown
2025-09-06 5:50 ` Al Viro
2025-09-06 5:52 ` Al Viro
2025-09-06 6:08 ` NeilBrown
2025-09-06 4:57 ` [PATCH 2/6] VFS/ovl: add lookup_one_positive_killable() NeilBrown
2025-09-06 9:44 ` Amir Goldstein
2025-09-08 2:07 ` NeilBrown
2025-09-08 7:09 ` Amir Goldstein
2025-09-09 2:14 ` NeilBrown
2025-09-06 4:57 ` [PATCH 3/6] VFS: discard err2 in filename_create() NeilBrown
2025-09-06 4:57 ` [PATCH 4/6] VFS: unify old_mnt_idmap and new_mnt_idmap in renamedata NeilBrown
2025-09-15 12:10 ` Christian Brauner
2025-09-19 22:54 ` NeilBrown
2025-09-19 23:17 ` Al Viro
2025-09-19 23:44 ` NeilBrown
2025-09-06 4:57 ` [PATCH 5/6] VFS/audit: introduce kern_path_parent() for audit NeilBrown
2025-09-07 2:17 ` kernel test robot [this message]
2025-09-06 4:57 ` [PATCH 6/6] VFS: rename kern_path_locked() to kern_path_removing() NeilBrown
2025-09-06 9:09 ` Amir Goldstein
2025-09-06 9:29 ` NeilBrown
2025-09-06 10:35 ` Amir Goldstein
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=202509070916.8uBFTDCH-lkp@intel.com \
--to=lkp@intel.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=neilb@ownmail.net \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
/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).