From: "Daniel P. Berrangé" <berrange@redhat.com>
To: marcandre.lureau@redhat.com
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH 2/4] chardev: fix qemu_chr_open_fd() with fd_in==fd_out
Date: Tue, 3 Aug 2021 09:44:08 +0100 [thread overview]
Message-ID: <YQkB2OVWERulr/UQ@redhat.com> (raw)
In-Reply-To: <20210723102825.1790112-3-marcandre.lureau@redhat.com>
On Fri, Jul 23, 2021 at 02:28:23PM +0400, marcandre.lureau@redhat.com wrote:
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> The "serial" chardev calls qemu_chr_open_fd() with the same fd. This
> may lead to double-close as each QIOChannel owns the fd.
>
> Instead, share the reference to the same QIOChannel.
>
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> ---
> chardev/char-fd.c | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/chardev/char-fd.c b/chardev/char-fd.c
> index ee85a52c06..32166182bf 100644
> --- a/chardev/char-fd.c
> +++ b/chardev/char-fd.c
> @@ -139,13 +139,24 @@ void qemu_chr_open_fd(Chardev *chr,
> qio_channel_set_name(QIO_CHANNEL(s->ioc_in), name);
> g_free(name);
> }
> - if (fd_out >= 0) {
> +
> + if (fd_out < 0) {
> + return;
> + }
> +
> + if (fd_out == fd_in) {
> + s->ioc_out = QIO_CHANNEL(object_ref(s->ioc_in));
> + name = g_strdup_printf("chardev-file-%s", chr->label);
> + qio_channel_set_name(QIO_CHANNEL(s->ioc_in), name);
> + g_free(name);
This is overwriting the name set a few lines earlier. I think the
code ought to be refactor to eliminate this duplication.
ie
if (fd_out == fd_in) {
s->ioc_out = s->ioc_in = QIO_CHANNEL(qio_channel_file_new_fd(fd_in));
....
} else {
s->ioc_in = QIO_CHANNEL(qio_channel_file_new_fd(fd_in));
...
s->ioc_out = QIO_CHANNEL(qio_channel_file_new_fd(fd_out));
...
}
> + } else {
> s->ioc_out = QIO_CHANNEL(qio_channel_file_new_fd(fd_out));
> name = g_strdup_printf("chardev-file-out-%s", chr->label);
> qio_channel_set_name(QIO_CHANNEL(s->ioc_out), name);
> g_free(name);
> - qemu_set_nonblock(fd_out);
> }
> +
> + qemu_set_nonblock(fd_out);
> }
>
> static void char_fd_class_init(ObjectClass *oc, void *data)
> --
> 2.32.0.264.g75ae10bc75
>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-08-03 8:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 10:28 [PATCH 0/4] chardev fixes marcandre.lureau
2021-07-23 10:28 ` [PATCH 1/4] chardev: fix qemu_chr_open_fd() being called with fd=-1 marcandre.lureau
2021-08-03 8:40 ` Daniel P. Berrangé
2021-08-04 11:11 ` Marc-André Lureau
2021-07-23 10:28 ` [PATCH 2/4] chardev: fix qemu_chr_open_fd() with fd_in==fd_out marcandre.lureau
2021-08-03 8:44 ` Daniel P. Berrangé [this message]
2021-07-23 10:28 ` [PATCH 3/4] chardev: remove needless class method marcandre.lureau
2021-08-02 18:53 ` Philippe Mathieu-Daudé
2021-08-03 8:45 ` Daniel P. Berrangé
2021-07-23 10:28 ` [PATCH 4/4] chardev: add some comments about the class methods marcandre.lureau
2021-08-03 8:46 ` Daniel P. Berrangé
2021-08-02 18:49 ` [PATCH 0/4] chardev fixes Marc-André Lureau
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=YQkB2OVWERulr/UQ@redhat.com \
--to=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--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).