linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: kbuild-all@lists.01.org,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: [djwong-xfs:zero-initialize-pmem-5.16 25/28] fs/iomap/buffered-io.c:943: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
Date: Thu, 7 Oct 2021 19:51:55 +0800	[thread overview]
Message-ID: <202110071951.xYAkEWMm-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2421 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git zero-initialize-pmem-5.16
head:   34b80c3d1203abd5fd64242ef25898c7d64166ca
commit: 262459cd3e039d51ed6f6c478e1b794dda7d9de8 [25/28] iomap: use accelerated zeroing on a block device to zero a file range
config: um-x86_64_defconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/commit/?id=262459cd3e039d51ed6f6c478e1b794dda7d9de8
        git remote add djwong-xfs https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git
        git fetch --no-tags djwong-xfs zero-initialize-pmem-5.16
        git checkout 262459cd3e039d51ed6f6c478e1b794dda7d9de8
        # save the attached .config to linux build tree
        make W=1 ARCH=um SUBARCH=x86_64

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> fs/iomap/buffered-io.c:943: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * Force a filesystem to write zeroes to mapped extents, even if they're
--
>> fs/iomap/buffered-io.c:948:1: warning: no previous prototype for 'iomap_zeroinit_range' [-Wmissing-prototypes]
     948 | iomap_zeroinit_range(struct inode *inode, loff_t pos, loff_t len,
         | ^~~~~~~~~~~~~~~~~~~~


vim +943 fs/iomap/buffered-io.c

   941	
   942	/**
 > 943	 * Force a filesystem to write zeroes to mapped extents, even if they're
   944	 * unwritten.  DAX files are not supported, and the caller should fsync the
   945	 * file before returning to userspace.
   946	 */
   947	int
 > 948	iomap_zeroinit_range(struct inode *inode, loff_t pos, loff_t len,
   949			     const struct iomap_ops *ops)
   950	{
   951		struct iomap_iter iter = {
   952			.inode		= inode,
   953			.pos		= pos,
   954			.len		= len,
   955			.flags		= IOMAP_ZERO,
   956		};
   957		int ret;
   958	
   959		if (IS_DAX(inode))
   960			return -EOPNOTSUPP;
   961	
   962		while ((ret = iomap_iter(&iter, ops)) > 0)
   963			iter.processed = iomap_zero_iter(&iter, NULL, false);
   964		return ret;
   965	}
   966	EXPORT_SYMBOL_GPL(iomap_zeroinit_range);
   967	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 9645 bytes --]

                 reply	other threads:[~2021-10-07 11:53 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=202110071951.xYAkEWMm-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=darrick.wong@oracle.com \
    --cc=djwong@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).