From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: devel@openvz.org, Liu Kui <kui.liu@virtuozzo.com>
Cc: azaitsev@virtuozzo.com
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:27:29 +0200 [thread overview]
Message-ID: <178946804979.2358389.173057515530639620.b4-ty@b4> (raw)
In-Reply-To: <20260915081612.60313-1-kui.liu@virtuozzo.com>
On Tue, 15 Sep 2026 16:16:12 +0800, Liu Kui wrote:
> fs/fuse kio: fix RPC response drop for large messages sent over RDMA
Applied to branch-rh10-6.12.0-211.52.1.20.x.vz10-ovz, will be released in rh10-6.12.0-211.52.1.20.5.vz10, thanks!
[1/1] fs/fuse kio: fix RPC response drop for large messages sent over RDMA
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/14d155b700cd
--
Konstantin Khorenko <khorenko@virtuozzo.com>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-09-15 10:28 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
2026-09-15 10:27 ` Konstantin Khorenko [this message]
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=178946804979.2358389.173057515530639620.b4-ty@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox