All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Hongbo Li <lihongbo22@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Christian Brauner <brauner@kernel.org>,
	"Darrick J. Wong" <djwong@kernel.org>,
	kernel test robot <lkp@intel.com>
Subject: Re: [linux-next:master 5773/9539] Warning: fs/iomap/buffered-io.c:624 function parameter 'private' not described in 'iomap_readahead'
Date: Mon, 26 Jan 2026 12:01:02 +0800	[thread overview]
Message-ID: <413ac550-ae70-4e38-be1d-4bd5e3be2447@linux.alibaba.com> (raw)
In-Reply-To: <202601261111.vIL9rhgD-lkp@intel.com>

Hi Hongbo,

On 2026/1/26 11:56, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   ca3a02fda4da8e2c1cb6baee5d72352e9e2cfaea
> commit: 8806f279244bf300dca2c99735d5a51cd24b86df [5773/9539] iomap: stash iomap read ctx in the private field of iomap_iter
> config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20260126/202601261111.vIL9rhgD-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/20260126/202601261111.vIL9rhgD-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/202601261111.vIL9rhgD-lkp@intel.com/
> 
> All warnings (new ones prefixed by >>):
> 
>>> Warning: fs/iomap/buffered-io.c:624 function parameter 'private' not described in 'iomap_readahead'
>>> Warning: fs/iomap/buffered-io.c:624 function parameter 'private' not described in 'iomap_readahead'

It seems the kernel-doc isn't updated, could you
submit another iomap patch to fix that?

  608 /**
  609  * iomap_readahead - Attempt to read pages from a file.
  610  * @ops: The operations vector for the filesystem.
  611  * @ctx: The ctx used for issuing readahead.

^ here.

  612  *
  613  * This function is for filesystems to call to implement their readahead
  614  * address_space operation.
  615  *
  616  * Context: The @ops callbacks may submit I/O (eg to read the addresses of
  617  * blocks from disc), and may wait for it.  The caller may be trying to
  618  * access a different page, and so sleeping excessively should be avoided.
  619  * It may allocate memory, but should avoid costly allocations.  This
  620  * function is called with memalloc_nofs set, so allocations will not cause
  621  * the filesystem to be reentered.
  622  */
  623 void iomap_readahead(const struct iomap_ops *ops,
  624                 struct iomap_read_folio_ctx *ctx, void *private)

Thanks,
Gao Xiang



> 


  reply	other threads:[~2026-01-26  4:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26  3:56 [linux-next:master 5773/9539] Warning: fs/iomap/buffered-io.c:624 function parameter 'private' not described in 'iomap_readahead' kernel test robot
2026-01-26  4:01 ` Gao Xiang [this message]
2026-01-26  6:18   ` Hongbo Li

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=413ac550-ae70-4e38-be1d-4bd5e3be2447@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=brauner@kernel.org \
    --cc=djwong@kernel.org \
    --cc=lihongbo22@huawei.com \
    --cc=lkp@intel.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 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.