From: Fei Li <fli@suse.com>
To: qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>, Fam Zheng <famz@redhat.com>
Subject: [Qemu-devel] [PATCH RFC v2 1/5] Fix segmentation fault when qemu_signal_init fails
Date: Thu, 29 Nov 2018 18:03:36 +0800 [thread overview]
Message-ID: <20181129100340.13823-2-fli@suse.com> (raw)
In-Reply-To: <20181129100340.13823-1-fli@suse.com>
When qemu_signal_init() fails in qemu_init_main_loop(), we return
without setting an error. Its callers crash then when they try to
report the error with error_report_err().
To avoid such segmentation fault, add a new Error parameter to make
the call trace to propagate the err to the final caller.
Fixes: 2f78e491d7b46542158ce0b8132ee4e05bc0ade4
Cc: Markus Armbruster <armbru@redhat.com>
Cc: Fam Zheng <famz@redhat.com>
Signed-off-by: Fei Li <fli@suse.com>
Reviewed-by: Fam Zheng <famz@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
---
util/main-loop.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/util/main-loop.c b/util/main-loop.c
index affe0403c5..443cb4cfe8 100644
--- a/util/main-loop.c
+++ b/util/main-loop.c
@@ -71,7 +71,7 @@ static void sigfd_handler(void *opaque)
}
}
-static int qemu_signal_init(void)
+static int qemu_signal_init(Error **errp)
{
int sigfd;
sigset_t set;
@@ -96,7 +96,7 @@ static int qemu_signal_init(void)
sigdelset(&set, SIG_IPI);
sigfd = qemu_signalfd(&set);
if (sigfd == -1) {
- fprintf(stderr, "failed to create signalfd\n");
+ error_setg_errno(errp, errno, "failed to create signalfd");
return -errno;
}
@@ -109,7 +109,7 @@ static int qemu_signal_init(void)
#else /* _WIN32 */
-static int qemu_signal_init(void)
+static int qemu_signal_init(Error **errp)
{
return 0;
}
@@ -148,7 +148,7 @@ int qemu_init_main_loop(Error **errp)
init_clocks(qemu_timer_notify_cb);
- ret = qemu_signal_init();
+ ret = qemu_signal_init(errp);
if (ret) {
return ret;
}
--
2.13.7
next prev parent reply other threads:[~2018-11-29 10:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 10:03 [Qemu-devel] [PATCH RFC v2 0/5] fix some segmentation faults and migration issues Fei Li
2018-11-29 10:03 ` Fei Li [this message]
2018-11-29 12:49 ` [Qemu-devel] [PATCH RFC v2 1/5] Fix segmentation fault when qemu_signal_init fails Markus Armbruster
2018-11-30 3:29 ` Fei Li
2018-11-29 10:03 ` [Qemu-devel] [PATCH RFC v2 2/5] qemu_thread_join: fix segmentation fault Fei Li
2018-11-29 10:03 ` [Qemu-devel] [PATCH RFC v2 3/5] migration: fix the multifd code when receiving less channels Fei Li
2018-11-29 14:46 ` Philippe Mathieu-Daudé
2018-11-30 3:45 ` Fei Li
2018-12-06 6:31 ` Fei Li
2018-11-29 10:03 ` [Qemu-devel] [PATCH RFC v2 4/5] migration: remove unused &local_err parameter in multifd_save_cleanup Fei Li
2018-11-29 14:50 ` Philippe Mathieu-Daudé
2018-11-29 14:52 ` Philippe Mathieu-Daudé
2018-11-30 5:12 ` Fei Li
2018-11-29 10:03 ` [Qemu-devel] [PATCH RFC v2 5/5] migration: add more error handling for postcopy_ram_enable_notify Fei Li
2018-11-30 9:49 ` Dr. David Alan Gilbert
2018-11-29 14:20 ` [Qemu-devel] [PATCH for-3.1? RFC v2 0/5] fix some segmentation faults and migration issues Eric Blake
2018-11-30 6:15 ` Fei Li
2018-11-30 15:57 ` 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=20181129100340.13823-2-fli@suse.com \
--to=fli@suse.com \
--cc=armbru@redhat.com \
--cc=famz@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).