llvm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Christian Brauner <christianvanbrauner@gmail.com>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Chaitanya Kulkarni <kch@nvidia.com>, Jens Axboe <axboe@kernel.dk>
Subject: [brauner-github:vfs-6.19.iomap 39/44] fs/overlayfs/file.c:376:10: error: use of undeclared identifier 'IOCB_DIO_CALLER_COMP'
Date: Sat, 15 Nov 2025 09:02:18 +0800	[thread overview]
Message-ID: <202511150802.j5gDUnim-lkp@intel.com> (raw)

tree:   https://github.com/brauner/linux.git vfs-6.19.iomap
head:   d9b964dbfd3e15635eae30da757e91c70f9d4628
commit: 56749ed317e256c6dc3ca83e246fc17479366f83 [39/44] fs, iomap: remove IOCB_DIO_CALLER_COMP
config: arm-randconfig-001-20251115 (https://download.01.org/0day-ci/archive/20251115/202511150802.j5gDUnim-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 0bba1e76581bad04e7d7f09f5115ae5e2989e0d9)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251115/202511150802.j5gDUnim-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/202511150802.j5gDUnim-lkp@intel.com/

All errors (new ones prefixed by >>):

>> fs/overlayfs/file.c:376:10: error: use of undeclared identifier 'IOCB_DIO_CALLER_COMP'
     376 |         ifl &= ~IOCB_DIO_CALLER_COMP;
         |                 ^~~~~~~~~~~~~~~~~~~~
   1 error generated.


vim +/IOCB_DIO_CALLER_COMP +376 fs/overlayfs/file.c

16914e6fc7e174 Miklos Szeredi    2018-07-18  344  
2a92e07edc5ede Miklos Szeredi    2018-07-18  345  static ssize_t ovl_write_iter(struct kiocb *iocb, struct iov_iter *iter)
2a92e07edc5ede Miklos Szeredi    2018-07-18  346  {
2a92e07edc5ede Miklos Szeredi    2018-07-18  347  	struct file *file = iocb->ki_filp;
2a92e07edc5ede Miklos Szeredi    2018-07-18  348  	struct inode *inode = file_inode(file);
d66907b51ba074 Amir Goldstein    2024-11-05  349  	struct file *realfile;
2a92e07edc5ede Miklos Szeredi    2018-07-18  350  	ssize_t ret;
c86243b090bc25 Vivek Goyal       2020-08-31  351  	int ifl = iocb->ki_flags;
a6293b3e285cd0 Amir Goldstein    2023-11-22  352  	struct backing_file_ctx ctx = {
a6293b3e285cd0 Amir Goldstein    2023-11-22  353  		.cred = ovl_creds(inode->i_sb),
f03b296e8b516d Amir Goldstein    2024-10-14  354  		.end_write = ovl_file_end_write,
a6293b3e285cd0 Amir Goldstein    2023-11-22  355  	};
2a92e07edc5ede Miklos Szeredi    2018-07-18  356  
2a92e07edc5ede Miklos Szeredi    2018-07-18  357  	if (!iov_iter_count(iter))
2a92e07edc5ede Miklos Szeredi    2018-07-18  358  		return 0;
2a92e07edc5ede Miklos Szeredi    2018-07-18  359  
2a92e07edc5ede Miklos Szeredi    2018-07-18  360  	inode_lock(inode);
2a92e07edc5ede Miklos Szeredi    2018-07-18  361  	/* Update mode */
2878dffc7db0b5 Christian Brauner 2022-04-04  362  	ovl_copyattr(inode);
2a92e07edc5ede Miklos Szeredi    2018-07-18  363  
d66907b51ba074 Amir Goldstein    2024-11-05  364  	realfile = ovl_real_file(file);
d66907b51ba074 Amir Goldstein    2024-11-05  365  	ret = PTR_ERR(realfile);
d66907b51ba074 Amir Goldstein    2024-11-05  366  	if (IS_ERR(realfile))
2a92e07edc5ede Miklos Szeredi    2018-07-18  367  		goto out_unlock;
2a92e07edc5ede Miklos Szeredi    2018-07-18  368  
c86243b090bc25 Vivek Goyal       2020-08-31  369  	if (!ovl_should_sync(OVL_FS(inode->i_sb)))
c86243b090bc25 Vivek Goyal       2020-08-31  370  		ifl &= ~(IOCB_DSYNC | IOCB_SYNC);
c86243b090bc25 Vivek Goyal       2020-08-31  371  
2d1b3bbc3dd56f Jens Axboe        2023-09-25  372  	/*
2d1b3bbc3dd56f Jens Axboe        2023-09-25  373  	 * Overlayfs doesn't support deferred completions, don't copy
2d1b3bbc3dd56f Jens Axboe        2023-09-25  374  	 * this property in case it is set by the issuer.
2d1b3bbc3dd56f Jens Axboe        2023-09-25  375  	 */
2d1b3bbc3dd56f Jens Axboe        2023-09-25 @376  	ifl &= ~IOCB_DIO_CALLER_COMP;
d66907b51ba074 Amir Goldstein    2024-11-05  377  	ret = backing_file_write_iter(realfile, iter, iocb, ifl, &ctx);
2a92e07edc5ede Miklos Szeredi    2018-07-18  378  
2a92e07edc5ede Miklos Szeredi    2018-07-18  379  out_unlock:
2a92e07edc5ede Miklos Szeredi    2018-07-18  380  	inode_unlock(inode);
2a92e07edc5ede Miklos Szeredi    2018-07-18  381  
2a92e07edc5ede Miklos Szeredi    2018-07-18  382  	return ret;
2a92e07edc5ede Miklos Szeredi    2018-07-18  383  }
2a92e07edc5ede Miklos Szeredi    2018-07-18  384  

:::::: The code at line 376 was first introduced by commit
:::::: 2d1b3bbc3dd56fc8364350eb93e5d67a05cb2c23 ovl: disable IOCB_DIO_CALLER_COMP

:::::: TO: Jens Axboe <axboe@kernel.dk>
:::::: CC: Christian Brauner <brauner@kernel.org>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-11-15  1:03 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=202511150802.j5gDUnim-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=christianvanbrauner@gmail.com \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=kch@nvidia.com \
    --cc=llvm@lists.linux.dev \
    --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;
as well as URLs for NNTP newsgroup(s).