From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: andrey.zhadchenko@virtuozzo.com,
Alexander Ivanov <alexander.ivanov@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v4 0/2] drivers/vhost/blk: add support for worker ioctls
Date: Tue, 17 Nov 2026 15:40:10 +0100 [thread overview]
Message-ID: <179492641021.990559.12151098327156812650.b4-ty@b4> (raw)
In-Reply-To: <20261116085139.2848797-1-alexander.ivanov@virtuozzo.com>
On Mon, 16 Nov 2026 09:51:37 +0100, Alexander Ivanov wrote:
> drivers/vhost/blk: add support for worker ioctls
>
> vhost-blk gets the mainstream worker ioctls, so userspace can move from
> our VHOST_SET_NWORKERS to them. Until it does, both interfaces live on
> the same device, and the workers VHOST_SET_NWORKERS installs are not
> counted in attachment_cnt: VHOST_FREE_WORKER can free a worker a vq
> still uses.
>
> [...]
Applied to branch-rh10-6.12.0-211.75.1.26.x.vz10-ovz, will be released in rh10-6.12.0-211.75.1.24.3.vz10, thanks!
[1/2] drivers/vhost: fix a use-after-free of VHOST_SET_NWORKERS workers
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/b3ed783d6715
[2/2] drivers/vhost/blk: add support for worker ioctls
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/6afc2f6416c3
--
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
prev parent reply other threads:[~2026-11-17 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 8:51 Alexander Ivanov
2026-11-16 8:51 ` [Devel] [PATCH hci-8.1 v4 1/2] drivers/vhost: fix a use-after-free of VHOST_SET_NWORKERS workers Alexander Ivanov
2026-11-16 8:57 ` no-reply
2026-11-16 8:51 ` [Devel] [PATCH hci-8.1 v4 2/2] drivers/vhost/blk: add support for worker ioctls Alexander Ivanov
2026-11-16 8:57 ` no-reply
2026-11-16 17:29 ` [Devel] [PATCH hci-8.1 v4 0/2] " Konstantin Khorenko
2026-11-17 14:40 ` 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=179492641021.990559.12151098327156812650.b4-ty@b4 \
--to=khorenko@virtuozzo.com \
--cc=alexander.ivanov@virtuozzo.com \
--cc=andrey.zhadchenko@virtuozzo.com \
--cc=devel@openvz.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox