From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Hanna Reitz" <hreitz@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>,
qemu-rust@nongnu.org,
"Richard Henderson" <richard.henderson@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Christian Schoenebeck" <qemu_oss@crudebyte.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-block@nongnu.org, "Stefan Weil" <sw@weilnetz.de>,
"Dr. David Alan Gilbert" <dave@treblig.org>,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
devel@lists.libvirt.org, "Paolo Bonzini" <pbonzini@redhat.com>
Subject: [PATCH v4 02/23] monitor: initialize global data from a constructor
Date: Thu, 25 Sep 2025 10:44:20 +0100 [thread overview]
Message-ID: <20250925094441.1651372-3-berrange@redhat.com> (raw)
In-Reply-To: <20250925094441.1651372-1-berrange@redhat.com>
Some monitor functions, most notably, monitor_cur() rely on global
data being initialized by 'monitor_init_globals()'. The latter is
called relatively late in startup. If code triggers error_report()
before monitor_init_globals() is called, QEMU will abort when
accessing the uninitialized monitor mutex.
The critical monitor global data must be initialized from a
constructor function, to improve the guarantee that it is done
before any possible calls to monitor_cur(). Not only that, but
the constructor must be marked to run before the default
constructor in case any of them trigger error reporting.
Note in particular that the RCU constructor will spawn a background
thread so we might even have non-constructor QEMU code running
concurrently with other constructors.
As a general note, constructors should be extrememly careful
about what QEMU code they invoke, as it cannot be guaranteed that
the process is fully initialized and so not all normal QEMU API
rules apply.
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Dr. David Alan Gilbert <dave@treblig.org>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Fixes: e69ee454b5f9 (monitor: Make current monitor a per-coroutine property)
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
---
monitor/monitor.c | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/monitor/monitor.c b/monitor/monitor.c
index c5a5d30877..da54e1b1ce 100644
--- a/monitor/monitor.c
+++ b/monitor/monitor.c
@@ -704,18 +704,22 @@ void monitor_cleanup(void)
}
}
-static void monitor_qapi_event_init(void)
+/*
+ * Initialize static vars that have no deps on external
+ * module initialization, and are required for external
+ * functions to call things like monitor_cur()
+ */
+static void __attribute__((__constructor__(QEMU_CONSTRUCTOR_EARLY)))
+monitor_init_static(void)
{
+ qemu_mutex_init(&monitor_lock);
+ coroutine_mon = g_hash_table_new(NULL, NULL);
monitor_qapi_event_state = g_hash_table_new(qapi_event_throttle_hash,
qapi_event_throttle_equal);
}
void monitor_init_globals(void)
{
- monitor_qapi_event_init();
- qemu_mutex_init(&monitor_lock);
- coroutine_mon = g_hash_table_new(NULL, NULL);
-
/*
* The dispatcher BH must run in the main loop thread, since we
* have commands assuming that context. It would be nice to get
--
2.50.1
next prev parent reply other threads:[~2025-09-25 9:49 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 9:44 [PATCH v4 00/23] util: sync error_report & qemu_log output more closely Daniel P. Berrangé
2025-09-25 9:44 ` [PATCH v4 01/23] include: define constant for early constructor priority Daniel P. Berrangé
2025-09-25 9:44 ` Daniel P. Berrangé [this message]
2025-09-25 9:44 ` [PATCH v4 03/23] system: unconditionally enable thread naming Daniel P. Berrangé
2025-09-25 9:44 ` [PATCH v4 04/23] util: expose qemu_thread_set_name Daniel P. Berrangé
2025-09-25 9:52 ` Philippe Mathieu-Daudé
2025-09-25 9:44 ` [PATCH v4 05/23] audio: make jackaudio use qemu_thread_set_name Daniel P. Berrangé
2025-09-25 9:44 ` [PATCH v4 06/23] util: set the name for the 'main' thread Daniel P. Berrangé
2025-09-25 9:44 ` [PATCH v4 07/23] util: add API to fetch the current thread name Daniel P. Berrangé
2025-09-25 21:13 ` Eric Blake
2025-09-25 9:44 ` [PATCH v4 08/23] log: avoid repeated prefix on incremental qemu_log calls Daniel P. Berrangé
2025-09-25 9:44 ` [PATCH v4 09/23] util: introduce some API docs for logging APIs Daniel P. Berrangé
2025-09-25 21:18 ` Eric Blake
2025-09-25 9:44 ` [PATCH v4 10/23] ui/vnc: remove use of error_printf_unless_qmp() Daniel P. Berrangé
2025-09-25 9:44 ` [PATCH v4 11/23] monitor: remove redundant error_[v]printf_unless_qmp Daniel P. Berrangé
2025-09-25 9:44 ` [PATCH v4 12/23] monitor: refactor error_vprintf() Daniel P. Berrangé
2025-09-25 9:44 ` [PATCH v4 13/23] monitor: move error_vprintf back to error-report.c Daniel P. Berrangé
2025-09-25 21:20 ` Eric Blake
2025-09-25 9:44 ` [PATCH v4 14/23] monitor: introduce monitor_cur_is_hmp() helper Daniel P. Berrangé
2025-09-25 19:41 ` Richard Henderson
2025-09-25 9:44 ` [PATCH v4 15/23] util: don't skip error prefixes when QMP is active Daniel P. Berrangé
2025-09-25 9:44 ` [PATCH v4 16/23] util: fix interleaving of error & trace output Daniel P. Berrangé
2025-09-25 9:44 ` [PATCH v4 17/23] util: fix interleaving of error prefixes Daniel P. Berrangé
2025-09-25 9:56 ` Philippe Mathieu-Daudé
2025-09-25 9:44 ` [PATCH v4 18/23] util: introduce common helper for error-report & log code Daniel P. Berrangé
2025-09-25 9:44 ` [PATCH v4 19/23] util: convert error-report & log to message API for timestamp Daniel P. Berrangé
2025-09-25 9:44 ` [PATCH v4 20/23] util: add support for formatting a workload name in messages Daniel P. Berrangé
2025-09-25 9:59 ` Philippe Mathieu-Daudé
2025-09-25 11:25 ` Philippe Mathieu-Daudé
2025-09-25 9:44 ` [PATCH v4 21/23] util: add support for formatting a program " Daniel P. Berrangé
2025-09-25 9:59 ` Philippe Mathieu-Daudé
2025-09-25 11:23 ` Philippe Mathieu-Daudé
2025-09-25 9:44 ` [PATCH v4 22/23] util: add support for formatting thread info " Daniel P. Berrangé
2025-09-25 10:00 ` Philippe Mathieu-Daudé
2025-09-25 9:44 ` [PATCH v4 23/23] util: add brackets around guest name in message context Daniel P. Berrangé
2025-09-25 10:01 ` Philippe Mathieu-Daudé
2025-09-25 11:25 ` Philippe Mathieu-Daudé
2025-09-25 10:22 ` [PATCH v4 00/23] util: sync error_report & qemu_log output more closely Philippe Mathieu-Daudé
2025-09-25 10:31 ` Daniel P. Berrangé
2025-09-25 11:21 ` Philippe Mathieu-Daudé
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=20250925094441.1651372-3-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=dave@treblig.org \
--cc=devel@lists.libvirt.org \
--cc=hreitz@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-rust@nongnu.org \
--cc=qemu_oss@crudebyte.com \
--cc=richard.henderson@linaro.org \
--cc=sw@weilnetz.de \
/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).