From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>,
Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>,
Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
Konstantin Khorenko <khorenko@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 0/2] vfio, exec: two mainline fixes that Oracle carries
Date: Wed, 04 Nov 2026 20:22:38 +0100 [thread overview]
Message-ID: <179382015819.2760255.10443844965041002141.b4-ty@b4> (raw)
In-Reply-To: <20261014-b4-prep-khorenko-vstor-149847-6-vfio-exec-ms-backports-v1-0-07b4e541d4ec@virtuozzo.com>
On Wed, 14 Oct 2026 19:16:25 +0200, Konstantin Khorenko wrote:
> vfio, exec: two mainline fixes that Oracle carries
>
> Two mainline fixes, independent of the MADV_DOEXEC series, found while
> comparing our tree with UEK8. Both are in linux-6.12.y as well and
> apply to the 211.52.1.22.x branch directly.
>
> - 1: vfio_mig_get_next_state() spins forever under the driver's state
> mutex when userspace asks for the blocked arc STOP_COPY -> PRE_COPY.
> Reproduced with the mtty sample driver: a soft lockup before, EINVAL
> after.
> - 2: do_close_on_exec() ran under exec_update_lock, so a FUSE daemon
> that inspects the exec'ing process (for example /proc/PID/maps) from
> its FLUSH handler deadlocked exec. Reproduced with a small FUSE
> filesystem: a deadlock before, a normal exec after.
>
> [...]
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.18.vz10, thanks!
[1/2] ms/vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/8f215ebf4783
[2/2] ms/exec: do_close_on_exec() before taking exec_update_lock
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/0a91ee4f869b
--
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-04 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 17:16 Konstantin Khorenko
2026-10-14 17:16 ` [Devel] [PATCH hci-8.1 1/2] ms/vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc Konstantin Khorenko
2026-10-14 17:34 ` no-reply
2026-10-14 17:16 ` [Devel] [PATCH hci-8.1 2/2] ms/exec: do_close_on_exec() before taking exec_update_lock Konstantin Khorenko
2026-10-14 17:35 ` no-reply
2026-11-04 19:22 ` 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=179382015819.2760255.10443844965041002141.b4-ty@b4 \
--to=khorenko@virtuozzo.com \
--cc=andrey.drobyshev@virtuozzo.com \
--cc=devel@openvz.org \
--cc=ptikhomirov@virtuozzo.com \
--cc=vasileios.almpanis@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.