From: kernel test robot <[email protected]>
To: "Alexander V. Buev" <[email protected]>, [email protected]
Cc: [email protected], [email protected],
Jens Axboe <[email protected]>, Christoph Hellwig <[email protected]>,
"Martin K . Petersen" <[email protected]>,
Pavel Begunkov <[email protected]>,
Chaitanya Kulkarni <[email protected]>,
Mikhail Malygin <[email protected]>,
[email protected], "Alexander V. Buev" <[email protected]>
Subject: Re: [PATCH v3 2/3] block: io-uring: add READV_PI/WRITEV_PI operations
Date: Fri, 9 Sep 2022 17:00:37 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Hi Alexander,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on axboe-block/for-next]
[also build test WARNING on linus/master v6.0-rc4 next-20220908]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Alexander-V-Buev/implement-direct-IO-with-integrity/20220909-143807
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
config: um-x86_64_defconfig (https://download.01.org/0day-ci/archive/20220909/[email protected]/config)
compiler: gcc-11 (Debian 11.3.0-5) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/eda3c42ce63fd33731304cc2ec9a8e1704270690
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Alexander-V-Buev/implement-direct-IO-with-integrity/20220909-143807
git checkout eda3c42ce63fd33731304cc2ec9a8e1704270690
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=um SUBARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <[email protected]>
All warnings (new ones prefixed by >>):
>> io_uring/rw_pi.c:181:5: warning: no previous prototype for 'kiocb_done' [-Wmissing-prototypes]
181 | int kiocb_done(struct io_kiocb *req, ssize_t ret,
| ^~~~~~~~~~
vim +/kiocb_done +181 io_uring/rw_pi.c
180
> 181 int kiocb_done(struct io_kiocb *req, ssize_t ret,
182 unsigned int issue_flags)
183 {
184 struct io_async_rw_pi *arw = req->async_data;
185 struct io_rw_pi *rw = io_kiocb_to_cmd(req, struct io_rw_pi);
186
187 /* add previously done IO, if any */
188 if (req_has_async_data(req) && arw->data.bytes_done > 0) {
189 if (ret < 0)
190 ret = arw->data.bytes_done;
191 else
192 ret += arw->data.bytes_done;
193 }
194
195 if (req->flags & REQ_F_CUR_POS)
196 req->file->f_pos = rw->kiocb.ki_pos;
197 if (ret >= 0 && (rw->kiocb.ki_complete == io_complete_rw)) {
198 if (!__io_complete_rw_common(req, ret)) {
199 io_req_set_res(req, req->cqe.res, 0);
200 return IOU_OK;
201 }
202 } else {
203 io_rw_done(&rw->kiocb, ret);
204 }
205
206 if (req->flags & REQ_F_REISSUE) {
207 req->flags &= ~REQ_F_REISSUE;
208 if (io_resubmit_prep(req))
209 io_req_task_queue_reissue(req);
210 else
211 io_req_task_queue_fail(req, ret);
212 }
213 return IOU_ISSUE_SKIP_COMPLETE;
214 }
215
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-09-09 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 6:32 [PATCH v3 0/3] implement direct IO with integrity Alexander V. Buev
2022-09-09 6:32 ` [PATCH v3 1/3] block: bio-integrity: add PI iovec to bio Alexander V. Buev
2022-09-09 6:32 ` [PATCH v3 2/3] block: io-uring: add READV_PI/WRITEV_PI operations Alexander V. Buev
2022-09-09 9:00 ` kernel test robot
2022-09-09 9:00 ` kernel test robot [this message]
2022-09-09 6:32 ` [PATCH v3 3/3] block: fops: handle IOCB_USE_PI in direct IO Alexander V. Buev
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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