From: kernel test robot <lkp@intel.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v2] vfs: remove the excl argument from the ->create() inode_operation
Date: Sun, 9 Nov 2025 21:15:07 +0800 [thread overview]
Message-ID: <202511092147.DCEwFtVj-lkp@intel.com> (raw)
In-Reply-To: <20251107-create-excl-v2-1-f678165d7f3f@kernel.org>
Hi Jeff,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 76ddfe7d66d631e5e31ef4e5dd59797fa03acbf7]
url: https://github.com/intel-lab-lkp/linux/commits/Jeff-Layton/vfs-remove-the-excl-argument-from-the-create-inode_operation/20251107-230938
base: 76ddfe7d66d631e5e31ef4e5dd59797fa03acbf7
patch link: https://lore.kernel.org/r/20251107-create-excl-v2-1-f678165d7f3f%40kernel.org
patch subject: [PATCH v2] vfs: remove the excl argument from the ->create() inode_operation
config: i386-randconfig-002-20251109 (https://download.01.org/0day-ci/archive/20251109/202511092147.DCEwFtVj-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251109/202511092147.DCEwFtVj-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/202511092147.DCEwFtVj-lkp@intel.com/
All warnings (new ones prefixed by >>):
fs/vboxsf/dir.c: In function 'vboxsf_dir_mkfile':
fs/vboxsf/dir.c:303:63: error: 'excl' undeclared (first use in this function)
303 | return vboxsf_dir_create(parent, dentry, mode, false, excl, NULL);
| ^~~~
fs/vboxsf/dir.c:303:63: note: each undeclared identifier is reported only once for each function it appears in
>> fs/vboxsf/dir.c:304:1: warning: control reaches end of non-void function [-Wreturn-type]
304 | }
| ^
vim +304 fs/vboxsf/dir.c
0fd16957664845 Hans de Goede 2019-12-12 298
6c960e68aaed33 Christian Brauner 2023-01-13 299 static int vboxsf_dir_mkfile(struct mnt_idmap *idmap,
549c7297717c32 Christian Brauner 2021-01-21 300 struct inode *parent, struct dentry *dentry,
695fb862eadb82 Jeff Layton 2025-11-07 301 umode_t mode)
0fd16957664845 Hans de Goede 2019-12-12 302 {
ab0c29687bc7a8 Hans de Goede 2021-01-21 @303 return vboxsf_dir_create(parent, dentry, mode, false, excl, NULL);
0fd16957664845 Hans de Goede 2019-12-12 @304 }
0fd16957664845 Hans de Goede 2019-12-12 305
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-11-09 13:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 15:05 [PATCH v2] vfs: remove the excl argument from the ->create() inode_operation Jeff Layton
2025-11-07 15:05 ` Jeff Layton
2025-11-07 15:05 ` [f2fs-dev] " Jeff Layton via Linux-f2fs-devel
2025-11-07 22:29 ` NeilBrown
2025-11-07 22:29 ` NeilBrown
2025-11-07 22:29 ` [f2fs-dev] " NeilBrown
2025-11-07 22:35 ` LLM disclosure (was: [PATCH v2] vfs: remove the excl argument from the ->create() inode_operation) Jonathan Corbet
2025-11-07 22:35 ` Jonathan Corbet
2025-11-07 22:35 ` [f2fs-dev] " Jonathan Corbet
2025-11-07 23:19 ` Jeff Layton
2025-11-07 23:19 ` Jeff Layton
2025-11-07 23:19 ` [f2fs-dev] " Jeff Layton via Linux-f2fs-devel
2025-11-07 23:37 ` NeilBrown
2025-11-07 23:37 ` NeilBrown
2025-11-07 23:37 ` [f2fs-dev] " NeilBrown
2025-11-08 6:12 ` [PATCH v2] vfs: remove the excl argument from the ->create() inode_operation Dominique Martinet
2025-11-08 6:12 ` Dominique Martinet
2025-11-08 6:12 ` [f2fs-dev] " Dominique Martinet
2025-11-08 9:19 ` Bagas Sanjaya
2025-11-08 9:19 ` Bagas Sanjaya
2025-11-09 11:25 ` kernel test robot
2025-11-09 11:48 ` Jeff Layton
2025-11-09 13:15 ` kernel test robot [this message]
2025-11-10 4:35 ` kernel test robot
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=202511092147.DCEwFtVj-lkp@intel.com \
--to=lkp@intel.com \
--cc=jlayton@kernel.org \
--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.