From: kernel test robot <lkp@intel.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Miklos Szeredi <mszeredi@redhat.com>,
linux-doc@vger.kernel.org
Subject: fs/overlayfs/util.c:352: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
Date: Sun, 12 Nov 2023 16:26:44 +0800 [thread overview]
Message-ID: <202311121628.byHp8tkv-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 1b907d0507354b74a4f2c286380cd6059af79248
commit: ad0af7104dadccd55cd2b390271677fac142650f vfs: introduce inode 'inuse' lock
date: 6 years ago
config: x86_64-randconfig-a001-20230604 (https://download.01.org/0day-ci/archive/20231112/202311121628.byHp8tkv-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/20231112/202311121628.byHp8tkv-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/202311121628.byHp8tkv-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/overlayfs/util.c:352: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Caller must hold a reference to inode to prevent it from being freed while
vim +352 fs/overlayfs/util.c
350
351 /**
> 352 * Caller must hold a reference to inode to prevent it from being freed while
353 * it is marked inuse.
354 */
355 bool ovl_inuse_trylock(struct dentry *dentry)
356 {
357 struct inode *inode = d_inode(dentry);
358 bool locked = false;
359
360 spin_lock(&inode->i_lock);
361 if (!(inode->i_state & I_OVL_INUSE)) {
362 inode->i_state |= I_OVL_INUSE;
363 locked = true;
364 }
365 spin_unlock(&inode->i_lock);
366
367 return locked;
368 }
369
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-12 8:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202311121628.byHp8tkv-lkp@intel.com \
--to=lkp@intel.com \
--cc=amir73il@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®