From: Kevin Wolf <kwolf@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Hanna Reitz <hreitz@redhat.com>,
qemu-block@nongnu.org, Eric Blake <eblake@redhat.com>,
Mads Ynddal <mads@ynddal.dk>
Subject: Re: [PATCH] trace/simple: Fix hang when using simpletrace with fork()
Date: Wed, 26 Feb 2025 10:29:59 +0100 [thread overview]
Message-ID: <Z77fF-7pdWTwRbt9@redhat.com> (raw)
In-Reply-To: <20250226085015.1143991-1-thuth@redhat.com>
Am 26.02.2025 um 09:50 hat Thomas Huth geschrieben:
> When compiling QEMU with --enable-trace-backends=simple , the
> iotest 233 is currently hanging. This happens because qemu-nbd
> calls trace_init_backends() first - which causes simpletrace to
> install its writer thread and the atexit() handler - before
> calling fork(). But the simpletrace writer thread is then only
> available in the parent process, not in the child process anymore.
> Thus when the child process exits, its atexit handler waits forever
> on the trace_empty_cond condition to be set by the non-existing
> writer thread, so the process never finishes.
>
> Fix it by installing a pthread_atfork() handler, too, which
> makes sure that the trace_writeout_enabled variable gets set
> to false again in the child process, so we can use it in the
> atexit() handler to check whether we still need to wait on the
> writer thread or not.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
I can see how this would fix the hang, but do we actually get the trace
events written out somewhere then? Or do we need to make sure that the
child process has a writer thread, too?
Of course, the question would then be how the two processes writing into
the same trace file interact.
Kevin
next prev parent reply other threads:[~2025-02-26 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 8:50 [PATCH] trace/simple: Fix hang when using simpletrace with fork() Thomas Huth
2025-02-26 9:15 ` Daniel P. Berrangé
2025-02-26 9:38 ` Thomas Huth
2025-02-26 9:53 ` Daniel P. Berrangé
2025-02-27 7:05 ` Stefan Hajnoczi
2025-02-26 9:29 ` Kevin Wolf [this message]
2025-02-26 9:51 ` Daniel P. Berrangé
2025-02-27 19:30 ` 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=Z77fF-7pdWTwRbt9@redhat.com \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=mads@ynddal.dk \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/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).