All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Liu Kui <kui.liu@virtuozzo.com>
Cc: azaitsev@virtuozzo.com, devel@openvz.org
Subject: Re: [Devel] [PATCH VZ10 v2] fs/fuse kio: fix RPC response drop for large messages sent over RDMA
Date: Tue, 15 Sep 2026 12:12:29 +0200	[thread overview]
Message-ID: <178946714943.2358389.16104120233529296356.b4-review@b4> (raw)
In-Reply-To: <20260915081612.60313-1-kui.liu@virtuozzo.com>

> @@ -931,6 +928,8 @@ static int rio_handle_rx_read_ack(struct pcs_rdmaio *rio,
>  
>  	list_for_each_entry(tx, &rio->active_txs, list)
>  		if (tx->xid == rack->xid) {
> +			rio_msg_sent(rio, NULL, tx->msg, 1);
> +			tx->msg = NULL;
>  			list_del(&tx->list);
>  			rio_handle_tx(rio, tx, !rack->status);
>  			return 0;

i will apply the current version of the patch right now, but i would suggest to
reorder the code here in a separate patch, something like this:

                        struct pcs_msg *msg = tx->msg;

                        list_del(&tx->list);
                        tx->msg = NULL;
                        rio_msg_sent(rio, NULL, msg, 1);
                        rio_handle_tx(rio, tx, !rack->status);

So you first remove and nullify the tx->msg, and only after that call msg->done().
Yes, right now there is no bug here:
pcs_rdma_next_timeout() is the only reader of the active_txs[0]->msg and is
called under ep->mutex we hold here, but still it's a good practice.

Reviewed-by: Konstantin Khorenko <khorenko@virtuozzo.com>

-- 
Konstantin Khorenko <khorenko@virtuozzo.com>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

  reply	other threads:[~2026-09-15 10:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  8:16 Liu Kui
2026-09-15 10:12 ` Konstantin Khorenko [this message]
2026-09-15 10:27 ` Konstantin Khorenko
2026-09-15 10:28 ` Konstantin Khorenko

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=178946714943.2358389.16104120233529296356.b4-review@b4 \
    --to=khorenko@virtuozzo.com \
    --cc=azaitsev@virtuozzo.com \
    --cc=devel@openvz.org \
    --cc=kui.liu@virtuozzo.com \
    /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.