From: Paolo Bonzini <pbonzini@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Alberto Garcia" <berto@igalia.com>
Cc: QEMU <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 3/3] char-socket: Lock tcp_chr_disconnect() and socket_reconnect_timeout()
Date: Thu, 7 Feb 2019 16:05:38 +0100 [thread overview]
Message-ID: <38cce726-69b6-d7cc-6392-0bbabfc067ca@redhat.com> (raw)
In-Reply-To: <CAJ+F1CJh5vJa_py=eChkZCW-+zbuU1GmdFWcfSYg+=t8ukwYNg@mail.gmail.com>
On 07/02/19 15:46, Marc-André Lureau wrote:
> That looks like a subset of "[Qemu-devel] Segfaults in chardev due to
> races". The problem is likely to occur with other chardevs I am
> afraid.
Yes, it could possibly happen with pty at least. However, Alberto's
patch is a start.
Paolo
prev parent reply other threads:[~2019-02-07 15:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 13:23 [Qemu-devel] [PATCH 0/3] char-socket: Fix race condition Alberto Garcia
2019-02-07 13:23 ` [Qemu-devel] [PATCH 1/3] main-loop: Don't leak GSources attached to a GMainContext Alberto Garcia
2019-02-07 13:25 ` Alberto Garcia
2019-02-07 14:21 ` Daniel P. Berrangé
2019-02-07 14:23 ` Marc-André Lureau
2019-02-07 14:24 ` Marc-André Lureau
2019-02-07 14:27 ` Alberto Garcia
2019-02-07 14:43 ` Marc-André Lureau
2019-02-07 14:47 ` Alberto Garcia
2019-02-07 13:23 ` [Qemu-devel] [PATCH 2/3] main-loop: Add qemu_idle_add() Alberto Garcia
2019-02-07 14:24 ` Daniel P. Berrangé
2019-02-07 14:28 ` Marc-André Lureau
2019-02-07 13:23 ` [Qemu-devel] [PATCH 3/3] char-socket: Lock tcp_chr_disconnect() and socket_reconnect_timeout() Alberto Garcia
2019-02-07 14:26 ` Daniel P. Berrangé
2019-02-08 8:50 ` Alberto Garcia
2019-02-08 9:34 ` Alberto Garcia
2019-02-08 13:46 ` Paolo Bonzini
2019-02-08 15:01 ` Alberto Garcia
2019-02-08 17:27 ` Paolo Bonzini
2019-02-07 14:46 ` Marc-André Lureau
2019-02-07 15:05 ` Paolo Bonzini [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=38cce726-69b6-d7cc-6392-0bbabfc067ca@redhat.com \
--to=pbonzini@redhat.com \
--cc=berto@igalia.com \
--cc=marcandre.lureau@gmail.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).