From: Fabiano Rosas <farosas@suse.de>
To: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Cédric Le Goater" <clg@redhat.com>,
"Peter Xu" <peterx@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Avihai Horon <avihaih@nvidia.com>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/3] vfio/migration: Max in-flight VFIO device state buffer count limit
Date: Tue, 01 Jul 2025 15:29:26 -0300 [thread overview]
Message-ID: <874ivv69yx.fsf@suse.de> (raw)
In-Reply-To: <0e88a253e06647f6c01bdeba45848501b3631bd3.1750787338.git.maciej.szmigiero@oracle.com>
"Maciej S. Szmigiero" <mail@maciej.szmigiero.name> writes:
> From: "Maciej S. Szmigiero" <maciej.szmigiero@oracle.com>
>
> Allow capping the maximum count of in-flight VFIO device state buffers
> queued at the destination, otherwise a malicious QEMU source could
> theoretically cause the target QEMU to allocate unlimited amounts of memory
> for buffers-in-flight.
>
> Since this is not expected to be a realistic threat in most of VFIO live
> migration use cases and the right value depends on the particular setup
> disable the limit by default by setting it to UINT64_MAX.
>
> Signed-off-by: Maciej S. Szmigiero <maciej.szmigiero@oracle.com>
Reviewed-by: Fabiano Rosas <farosas@suse.de>
next prev parent reply other threads:[~2025-07-01 18:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 17:51 [PATCH 0/3] VFIO multifd device state transfer patches for QEMU 10.1 Maciej S. Szmigiero
2025-06-24 17:51 ` [PATCH 1/3] vfio/migration: Max in-flight VFIO device state buffer count limit Maciej S. Szmigiero
2025-07-01 18:29 ` Fabiano Rosas [this message]
2025-07-07 9:29 ` Avihai Horon
2025-07-07 10:47 ` Maciej S. Szmigiero
2025-07-15 8:57 ` Cédric Le Goater
2025-06-24 17:51 ` [PATCH 2/3] vfio/migration: Add x-migration-load-config-after-iter VFIO property Maciej S. Szmigiero
2025-07-01 18:29 ` Fabiano Rosas
2025-07-02 6:27 ` Cédric Le Goater
2025-07-02 6:31 ` Cédric Le Goater
2025-07-02 17:27 ` Maciej S. Szmigiero
2025-07-15 9:21 ` Cédric Le Goater
2025-07-08 8:34 ` Avihai Horon
2025-07-15 9:08 ` Cédric Le Goater
2025-07-15 9:21 ` Avihai Horon
2025-06-24 17:51 ` [PATCH 3/3] vfio/migration: Add also max in-flight VFIO device state buffers size limit Maciej S. Szmigiero
2025-07-01 18:29 ` Fabiano Rosas
2025-07-07 9:32 ` Avihai Horon
2025-07-14 9:46 ` [PATCH 0/3] VFIO multifd device state transfer patches for QEMU 10.1 Maciej S. Szmigiero
2025-07-15 9:25 ` 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=874ivv69yx.fsf@suse.de \
--to=farosas@suse.de \
--cc=alex.williamson@redhat.com \
--cc=avihaih@nvidia.com \
--cc=clg@redhat.com \
--cc=mail@maciej.szmigiero.name \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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 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.