From: Alex Williamson <alex.williamson@redhat.com>
To: Axel Rasmussen <axelrasmussen@google.com>
Cc: stable@vger.kernel.org, Ankit Agrawal <ankita@nvidia.com>,
Eric Auger <eric.auger@redhat.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
Kunwu Chan <chentao@kylinos.cn>,
Leah Rumancik <leah.rumancik@gmail.com>,
Miaohe Lin <linmiaohe@huawei.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Yi Liu <yi.l.liu@intel.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.9 0/3] Backport VFIO refactor to fix fork ordering bug
Date: Wed, 17 Jul 2024 15:44:25 -0600 [thread overview]
Message-ID: <20240717154425.43437eea.alex.williamson@redhat.com> (raw)
In-Reply-To: <20240717213339.1921530-1-axelrasmussen@google.com>
On Wed, 17 Jul 2024 14:33:36 -0700
Axel Rasmussen <axelrasmussen@google.com> wrote:
> 35e351780fa9 ("fork: defer linking file vma until vma is fully initialized")
> switched the ordering of vm_ops->open() and copy_page_range() on fork. This is a
> bug for VFIO, because it causes two problems:
>
> 1. Because open() is called before copy_page_range(), the range can conceivably
> have unmapped 'holes' in it. This causes the code underneath untrack_pfn() to
> WARN.
>
> 2. More seriously, open() is trying to guarantee that the entire range is
> zapped, so any future accesses in the child will result in the VFIO fault
> handler being called. Because we copy_page_range() *after* open() (and
> therefore after zapping), this guarantee is violatd.
>
> We can't revert 35e351780fa9, because it fixes a real bug for hugetlbfs. The fix
> is also not as simple as just reodering open() and copy_page_range(), as Miaohe
> points out in [1]. So, although these patches are kind of large for stable, just
> backport this refactoring which completely sidesteps the issue.
>
> Note that patch 2 is the key one here which fixes the issue. Patch 1 is a
> prerequisite required for patch 2 to build / work. This would almost be enough,
> but we might see significantly regressed performance. Patch 3 fixes that up,
> putting performance back on par with what it was before.
>
> Note [1] also has a more full discussion justifying taking these backports.
>
> [1]: https://lore.kernel.org/all/20240702042948.2629267-1-leah.rumancik@gmail.com/T/
>
> Alex Williamson (3):
> vfio: Create vfio_fs_type with inode per device
> vfio/pci: Use unmap_mapping_range()
> vfio/pci: Insert full vma on mmap'd MMIO fault
>
> drivers/vfio/device_cdev.c | 7 +
> drivers/vfio/group.c | 7 +
> drivers/vfio/pci/vfio_pci_core.c | 271 ++++++++-----------------------
> drivers/vfio/vfio_main.c | 44 +++++
> include/linux/vfio.h | 1 +
> include/linux/vfio_pci_core.h | 2 -
> 6 files changed, 125 insertions(+), 207 deletions(-)
>
> --
> 2.45.2.993.g49e7a77208-goog
>
LGTM
Reviewed-by: Alex Williamson <alex.williamson@redhat.com>
Thanks,
Alex
prev parent reply other threads:[~2024-07-17 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 21:33 Axel Rasmussen
2024-07-17 21:33 ` [PATCH 6.9 1/3] vfio: Create vfio_fs_type with inode per device Axel Rasmussen
2024-07-17 21:33 ` [PATCH 6.9 2/3] vfio/pci: Use unmap_mapping_range() Axel Rasmussen
2024-07-17 21:33 ` [PATCH 6.9 3/3] vfio/pci: Insert full vma on mmap'd MMIO fault Axel Rasmussen
2024-07-17 21:44 ` Alex Williamson [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=20240717154425.43437eea.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=ankita@nvidia.com \
--cc=axelrasmussen@google.com \
--cc=chentao@kylinos.cn \
--cc=eric.auger@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=leah.rumancik@gmail.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=yi.l.liu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®