From: "Landon Clipp" <landonclipp@gmail.com>
To: "Steve Sistare" <steven.sistare@oracle.com>, <qemu-devel@nongnu.org>
Cc: "Alex Williamson" <alex.williamson@redhat.com>,
"Cedric Le Goater" <clg@redhat.com>,
"Yi Liu" <yi.l.liu@intel.com>,
"Eric Auger" <eric.auger@redhat.com>,
"Zhenzhong Duan" <zhenzhong.duan@intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Peter Xu" <peterx@redhat.com>, "Fabiano Rosas" <farosas@suse.de>,
<qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org>
Subject: Re: [PATCH V6 06/21] backends/iommufd: change process ioctl
Date: Thu, 26 Mar 2026 13:34:42 -0700 [thread overview]
Message-ID: <DHD021CSIBZK.3PZ1A7CQUUBQU@gmail.com> (raw)
In-Reply-To: <1751493538-202042-7-git-send-email-steven.sistare@oracle.com>
Hello,
I'm running Linux 6.8.12 and when running QEMU 10.1 or above, it segfaults when
submitting the IOMMU_IOAS_CHANGE_PROCESS ioctl which is not supported on my
kernel. Here is an example strace:
3388260 22:48:30.540879 openat(AT_FDCWD, "/dev/iommu", O_RDWR|O_CLOEXEC) = 25
3388260 22:48:30.540942 ioctl(25, IOMMU_IOAS_CHANGE_PROCESS, 0x7ffe91d96490) = -1 ENOTTY (Inappropriate ioctl for device)
3388260 22:48:30.541003 close(25) = 0
3388260 22:48:30.541059 close(26) = 0
3388260 22:48:30.541120 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} ---
I heard through the grapevine that this is a known issue and was fixed. My
question is what QEMU version should I expect this fix to land and roughly what
the timeframe for it is (assuming it hasn't been landed already)?
Landon Clipp
next prev parent reply other threads:[~2026-03-26 20:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 21:58 [PATCH V6 00/21] Live update: vfio and iommufd Steve Sistare
2025-07-02 21:58 ` [PATCH V6 01/21] vfio-pci: preserve MSI Steve Sistare
2025-07-03 6:13 ` Cédric Le Goater
2025-07-02 21:58 ` [PATCH V6 02/21] vfio-pci: preserve INTx Steve Sistare
2025-07-03 6:13 ` Cédric Le Goater
2025-07-02 21:58 ` [PATCH V6 03/21] migration: close kvm after cpr Steve Sistare
2025-07-02 22:05 ` Steven Sistare
2025-07-04 9:50 ` Duan, Zhenzhong
2025-07-07 13:07 ` Steven Sistare
2025-07-08 3:04 ` Duan, Zhenzhong
2025-07-02 21:58 ` [PATCH V6 04/21] migration: cpr_get_fd_param helper Steve Sistare
2025-07-02 21:58 ` [PATCH V6 05/21] backends/iommufd: iommufd_backend_map_file_dma Steve Sistare
2025-07-02 21:58 ` [PATCH V6 06/21] backends/iommufd: change process ioctl Steve Sistare
2026-03-26 20:34 ` Landon Clipp [this message]
2026-03-27 1:30 ` Duan, Zhenzhong
2026-03-27 10:41 ` Cédric Le Goater
2025-07-02 21:58 ` [PATCH V6 07/21] physmem: qemu_ram_get_fd_offset Steve Sistare
2025-07-02 21:58 ` [PATCH V6 08/21] vfio/iommufd: use IOMMU_IOAS_MAP_FILE Steve Sistare
2025-07-02 21:58 ` [PATCH V6 09/21] vfio/iommufd: invariant device name Steve Sistare
2025-07-02 21:58 ` [PATCH V6 10/21] vfio/iommufd: add vfio_device_free_name Steve Sistare
2025-07-02 21:58 ` [PATCH V6 11/21] vfio/iommufd: device name blocker Steve Sistare
2025-07-02 21:58 ` [PATCH V6 12/21] vfio/iommufd: register container for cpr Steve Sistare
2025-07-03 2:42 ` Duan, Zhenzhong
2025-07-02 21:58 ` [PATCH V6 13/21] migration: vfio cpr state hook Steve Sistare
2025-07-03 2:44 ` Duan, Zhenzhong
2025-07-02 21:58 ` [PATCH V6 14/21] vfio/iommufd: cpr state Steve Sistare
2025-07-02 21:58 ` [PATCH V6 15/21] vfio/iommufd: preserve descriptors Steve Sistare
2025-07-02 21:58 ` [PATCH V6 16/21] vfio/iommufd: reconstruct device Steve Sistare
2025-07-02 21:58 ` [PATCH V6 17/21] vfio/iommufd: reconstruct hwpt Steve Sistare
2025-07-02 21:58 ` [PATCH V6 18/21] vfio/iommufd: change process Steve Sistare
2025-07-02 21:58 ` [PATCH V6 19/21] iommufd: preserve DMA mappings Steve Sistare
2025-07-02 21:58 ` [PATCH V6 20/21] vfio/container: delete old cpr register Steve Sistare
2025-07-02 21:58 ` [PATCH V6 21/21] vfio: doc changes for cpr Steve Sistare
2025-07-03 6:22 ` [PATCH V6 00/21] Live update: vfio and iommufd Cédric Le Goater
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=DHD021CSIBZK.3PZ1A7CQUUBQU@gmail.com \
--to=landonclipp@gmail.com \
--cc=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=eric.auger@redhat.com \
--cc=farosas@suse.de \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=steven.sistare@oracle.com \
--cc=yi.l.liu@intel.com \
--cc=zhenzhong.duan@intel.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.