From: kernel test robot <lkp@intel.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [axboe-block:io_uring-handle 3/3] io_uring/openclose.c:587:9: error: use of undeclared identifier 'IOU_OK'
Date: Fri, 6 Jun 2025 04:15:56 +0800 [thread overview]
Message-ID: <202506060420.OZdcUHlj-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git io_uring-handle
head: 7a590a5963086085ce58fee4cdf920e8fdd049f4
commit: 7a590a5963086085ce58fee4cdf920e8fdd049f4 [3/3] io_uring: add support for IORING_OP_OPEN_BY_HANDLE
config: s390-randconfig-002-20250606 (https://download.01.org/0day-ci/archive/20250606/202506060420.OZdcUHlj-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250606/202506060420.OZdcUHlj-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/202506060420.OZdcUHlj-lkp@intel.com/
All errors (new ones prefixed by >>):
>> io_uring/openclose.c:587:9: error: use of undeclared identifier 'IOU_OK'
587 | return IOU_OK;
| ^
1 error generated.
vim +/IOU_OK +587 io_uring/openclose.c
555
556 int io_open_by_handle(struct io_kiocb *req, unsigned int issue_flags)
557 {
558 struct io_open_handle *h = io_kiocb_to_cmd(req, struct io_open_handle);
559 const struct export_operations *eops;
560 int ret;
561
562 ret = get_path_from_fd(h->dirfd, &h->ctx.root);
563 if (ret < 0)
564 goto err;
565
566 eops = h->ctx.root.mnt->mnt_sb->s_export_op;
567 if (eops && eops->permission)
568 ret = eops->permission(&h->ctx, h->open_flags);
569 else
570 ret = may_decode_fh(&h->ctx, h->open_flags);
571 if (ret) {
572 path_put(&h->ctx.root);
573 goto err;
574 }
575
576 ret = __io_open_by_handle(req, issue_flags, eops);
577 io_req_set_res(req, ret, 0);
578 if (ret < 0) {
579 err:
580 req_set_fail(req);
581 return ret;
582 }
583
584 kfree(req->async_data);
585 req->async_data = NULL;
586 req->flags &= ~REQ_F_ASYNC_DATA;
> 587 return IOU_OK;
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-06-05 20:16 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=202506060420.OZdcUHlj-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--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