OpenVZ / Virtuozzo kernel development (devel@openvz.org)
 help / color / mirror / Atom feed
From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>,
	Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>,
	Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
Cc: devel@openvz.org
Subject: [Devel] [PATCH hci-8.1 0/2] vfio, exec: two mainline fixes that Oracle carries
Date: Wed, 14 Oct 2026 19:16:25 +0200	[thread overview]
Message-ID: <20261014-b4-prep-khorenko-vstor-149847-6-vfio-exec-ms-backports-v1-0-07b4e541d4ec@virtuozzo.com> (raw)

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.

Tested on a debug kernel: both reproducers, selftests/exec, a Container
start/exec/stop.

https://virtuozzo.atlassian.net/browse/VSTOR-150235

---
Jann Horn (1):
      ms/exec: do_close_on_exec() before taking exec_update_lock

Junrui Luo (1):
      ms/vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc

 drivers/vfio/vfio_main.c |  3 ++-
 fs/exec.c                | 22 ++++++++++++++--------
 2 files changed, 16 insertions(+), 9 deletions(-)
---
base-commit: defa968cbe8c38f1ff0231042dee07f00d27b2c9
change-id: 20261014-b4-prep-khorenko-vstor-149847-6-vfio-exec-ms-backports-0564f1b9331f

Best regards,
--  
Konstantin Khorenko <khorenko@virtuozzo.com>

_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

             reply	other threads:[~2026-10-14 17:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14 17:16 Konstantin Khorenko [this message]
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

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=20261014-b4-prep-khorenko-vstor-149847-6-vfio-exec-ms-backports-v1-0-07b4e541d4ec@virtuozzo.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox