From: Peter Xu <peterx@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: qemu-devel@nongnu.org, "Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH v2 2/2] migration/multifd: Ensure we're not given a socket for file migration
Date: Thu, 14 Mar 2024 11:10:12 -0400 [thread overview]
Message-ID: <ZfMTVApNl01-yS_v@x1n> (raw)
In-Reply-To: <20240313212824.16974-3-farosas@suse.de>
On Wed, Mar 13, 2024 at 06:28:24PM -0300, Fabiano Rosas wrote:
> When doing migration using the fd: URI, the incoming migration starts
> before the user has passed the file descriptor to QEMU. This means
> that the checks at migration_channels_and_transport_compatible()
> happen too soon and we need to allow a migration channel of type
> SOCKET_ADDRESS_TYPE_FD even though socket migration is not supported
> with multifd.
Hmm, bare with me if this is a stupid one.. why the incoming migration can
start _before_ the user passed in the fd?
IOW, why can't we rely on a single fd_is_socket() check for
SOCKET_ADDRESS_TYPE_FD in transport_supports_multi_channels()?
>
> The commit decdc76772 ("migration/multifd: Add mapped-ram support to
> fd: URI") was supposed to add a second check prior to starting
> migration to make sure a socket fd is not passed instead of a file fd,
> but failed to do so.
>
> Add the missing verification.
>
> Fixes: decdc76772 ("migration/multifd: Add mapped-ram support to fd: URI")
> Signed-off-by: Fabiano Rosas <farosas@suse.de>
> ---
> migration/fd.c | 8 ++++++++
> migration/file.c | 7 +++++++
> 2 files changed, 15 insertions(+)
>
> diff --git a/migration/fd.c b/migration/fd.c
> index 39a52e5c90..c07030f715 100644
> --- a/migration/fd.c
> +++ b/migration/fd.c
> @@ -22,6 +22,7 @@
> #include "migration.h"
> #include "monitor/monitor.h"
> #include "io/channel-file.h"
> +#include "io/channel-socket.h"
> #include "io/channel-util.h"
> #include "options.h"
> #include "trace.h"
> @@ -95,6 +96,13 @@ void fd_start_incoming_migration(const char *fdname, Error **errp)
> }
>
> if (migrate_multifd()) {
> + if (fd_is_socket(fd)) {
> + error_setg(errp,
> + "Multifd migration to a socket FD is not supported");
> + object_unref(ioc);
> + return;
> + }
> +
> file_create_incoming_channels(ioc, errp);
> } else {
> qio_channel_set_name(ioc, "migration-fd-incoming");
> diff --git a/migration/file.c b/migration/file.c
> index ddde0ca818..b6e8ba13f2 100644
> --- a/migration/file.c
> +++ b/migration/file.c
> @@ -15,6 +15,7 @@
> #include "file.h"
> #include "migration.h"
> #include "io/channel-file.h"
> +#include "io/channel-socket.h"
> #include "io/channel-util.h"
> #include "options.h"
> #include "trace.h"
> @@ -58,6 +59,12 @@ bool file_send_channel_create(gpointer opaque, Error **errp)
> int fd = fd_args_get_fd();
>
> if (fd && fd != -1) {
> + if (fd_is_socket(fd)) {
> + error_setg(errp,
> + "Multifd migration to a socket FD is not supported");
> + goto out;
> + }
> +
> ioc = qio_channel_file_new_dupfd(fd, errp);
> } else {
> ioc = qio_channel_file_new_path(outgoing_args.fname, flags, 0, errp);
> --
> 2.35.3
>
--
Peter Xu
next prev parent reply other threads:[~2024-03-14 15:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 21:28 [PATCH v2 0/2] migration mapped-ram fixes Fabiano Rosas
2024-03-13 21:28 ` [PATCH v2 1/2] migration: Fix iocs leaks during file and fd migration Fabiano Rosas
2024-03-14 15:10 ` Peter Xu
2024-03-13 21:28 ` [PATCH v2 2/2] migration/multifd: Ensure we're not given a socket for file migration Fabiano Rosas
2024-03-14 15:10 ` Peter Xu [this message]
2024-03-14 15:43 ` Peter Xu
2024-03-14 16:50 ` Fabiano Rosas
2024-03-14 17:58 ` Peter Xu
2024-03-14 16:44 ` Fabiano Rosas
2024-03-14 17:53 ` Peter Xu
2024-03-14 15:22 ` [PATCH v2 0/2] migration mapped-ram fixes Peter Xu
2024-03-14 16:55 ` Fabiano Rosas
2024-03-14 17:35 ` Peter Xu
2024-03-14 18:00 ` Peter Xu
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=ZfMTVApNl01-yS_v@x1n \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=farosas@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).