All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Fu <vincentfu@gmail.com>
To: Ankit Kumar <ankit.kumar@samsung.com>, axboe@kernel.dk
Cc: fio@vger.kernel.org
Subject: Re: [PATCH] engines/io_uring_cmd: skip pi verify checks for error cases
Date: Tue, 12 Dec 2023 09:40:51 -0500	[thread overview]
Message-ID: <1dd0e64e-029e-4689-a6c3-b2e0e5228dae@gmail.com> (raw)
In-Reply-To: <20231212144718.568406-1-ankit.kumar@samsung.com>

On 12/12/23 09:47, Ankit Kumar wrote:
> If any error is observed for read requests, skip all end to end data
> protection checks.
> 
> Signed-off-by: Ankit Kumar <ankit.kumar@samsung.com>
> ---
>   engines/io_uring.c | 6 ++++--
>   1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/engines/io_uring.c b/engines/io_uring.c
> index 5ae3135b..c0cb5a78 100644
> --- a/engines/io_uring.c
> +++ b/engines/io_uring.c
> @@ -468,10 +468,12 @@ static struct io_u *fio_ioring_cmd_event(struct thread_data *td, int event)
>   	cqe = &ld->cq_ring.cqes[index];
>   	io_u = (struct io_u *) (uintptr_t) cqe->user_data;
>   
> -	if (cqe->res != 0)
> +	if (cqe->res != 0) {
>   		io_u->error = -cqe->res;
> -	else
> +		return io_u;
> +	} else {
>   		io_u->error = 0;
> +	}
>   
>   	if (o->cmd_type == FIO_URING_CMD_NVME) {
>   		data = FILE_ENG_DATA(io_u->file);

Applied. Thanks.

      reply	other threads:[~2023-12-12 14:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20231212092942epcas5p28e0b580bf48a7d932f1d801a7d4226dd@epcas5p2.samsung.com>
2023-12-12 14:47 ` [PATCH] engines/io_uring_cmd: skip pi verify checks for error cases Ankit Kumar
2023-12-12 14:40   ` Vincent Fu [this message]

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=1dd0e64e-029e-4689-a6c3-b2e0e5228dae@gmail.com \
    --to=vincentfu@gmail.com \
    --cc=ankit.kumar@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=fio@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 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.