From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Liu Kui <kui.liu@virtuozzo.com>
Cc: devel@openvz.org, azaitsev@virtuozzo.com
Subject: Re: [Devel] [PATCH hci-8.1 0/2] fs/fuse kio: two fixes for the sockio transmit refactor
Date: Thu, 01 Oct 2026 14:05:52 +0200 [thread overview]
Message-ID: <179085635227.3679650.7758064137763149498.b4-ty@b4> (raw)
In-Reply-To: <20261001-sockio-sendmsg-empty-iter-v1-0-b876f4fbb9c7@virtuozzo.com>
On Thu, 01 Oct 2026 11:23:40 +0800, Liu Kui wrote:
> fs/fuse kio: two fixes for the sockio transmit refactor
>
> Follow-up to the sockio refactor, fixing two issues found in review:
> a latent infinite loop on an empty iter in do_sockio_sendmsg(), and
> iov_iter_sendpages_ok() missing the last page of a bvec with an
> unaligned bv_offset.
>
> [...]
Applied to branch-rh10-6.12.0-211.52.1.22.x.vz10-ovz, will be released in rh10-6.12.0-211.52.1.22.7.vz10, thanks!
[1/2] fs/fuse kio: don't spin on an empty iter in do_sockio_sendmsg()
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/668fd929529e
[2/2] fs/fuse kio: check every touched page in iov_iter_sendpages_ok()
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/0750a95935c5
--
Konstantin Khorenko <khorenko@virtuozzo.com>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
prev parent reply other threads:[~2026-10-01 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 3:23 Liu Kui
2026-10-01 3:23 ` [Devel] [PATCH hci-8.1 1/2] fs/fuse kio: don't spin on an empty iter in do_sockio_sendmsg() Liu Kui
2026-10-01 3:26 ` no-reply
2026-10-01 3:23 ` [Devel] [PATCH hci-8.1 2/2] fs/fuse kio: check every touched page in iov_iter_sendpages_ok() Liu Kui
2026-10-01 3:26 ` no-reply
2026-10-01 12:05 ` Konstantin Khorenko [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=179085635227.3679650.7758064137763149498.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 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.