From: Markus Armbruster <armbru@redhat.com>
To: Gal Hammer <ghammer@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>,
qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH v3] char: restore read callback on a reattached (hotplug) chardev
Date: Thu, 12 Dec 2013 13:02:44 +0100 [thread overview]
Message-ID: <8761quffa3.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <1386834932-2078-1-git-send-email-ghammer@redhat.com> (Gal Hammer's message of "Thu, 12 Dec 2013 09:55:32 +0200")
Gal Hammer <ghammer@redhat.com> writes:
> Fix a bug that was introduced in commit 386a5a1e. A removal of a device
> set the chr handlers to NULL. However when the device is plugged back,
> its read callback is not restored so data can't be transftered from the
> host to the guest (e.g. via the virtio-serial port).
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1027181
>
> Signed-off-by: Gal Hammer <ghammer@redhat.com>
>
> V3: - fix a typo in comment.
> - move the revision history after the "signed-off-by" tag.
Close, but no cigar :)
It needs to go below the '---' line.
> V2: - do not call chr_update_read_handler on device removal.
> - add asserts to verify chr_update_read_handler is not called
> with an assigned fd_in_tag to prevent fd leaks.
> - update fd and udp backends' chr_update_read_handler function
> so it won't remove fd_in to prevent a double release.
> ---
Right here is fine.
> qemu-char.c | 17 +++++++++++++++--
> 1 file changed, 15 insertions(+), 2 deletions(-)
[...]
next prev parent reply other threads:[~2013-12-12 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 7:55 [Qemu-devel] [PATCH v3] char: restore read callback on a reattached (hotplug) chardev Gal Hammer
2013-12-12 12:02 ` Markus Armbruster [this message]
2013-12-12 15:46 ` Eric Blake
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=8761quffa3.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=aliguori@amazon.com \
--cc=amit.shah@redhat.com \
--cc=ghammer@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 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.