All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fei Li <fli@suse.com>
To: qemu-devel@nongnu.org
Cc: armbru@redhat.com, dgilbert@redhat.com, famz@redhat.com,
	peterx@redhat.com, quintela@redhat.com
Subject: [Qemu-devel] [PATCH RFC v6 1/7] Fix segmentation fault when qemu_signal_init fails
Date: Mon, 29 Oct 2018 20:58:12 +0800	[thread overview]
Message-ID: <20181029125818.28720-2-fli@suse.com> (raw)
In-Reply-To: <20181029125818.28720-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.

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>
---
 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

  reply	other threads:[~2018-10-29 12:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 12:58 [Qemu-devel] [PATCH RFC v6 0/7] qemu_thread_create: propagate errors to callers to check Fei Li
2018-10-29 12:58 ` Fei Li [this message]
2018-10-29 12:58 ` [Qemu-devel] [PATCH RFC v6 2/7] qemu_init_vcpu: add a new Error parameter to propagate Fei Li
2018-10-29 12:58 ` [Qemu-devel] [PATCH RFC v6 3/7] qemu_thread_join: fix segmentation fault Fei Li
2018-10-29 12:58 ` [Qemu-devel] [PATCH RFC v6 4/7] migration: fix some segmentation faults when using multifd Fei Li
2018-10-29 12:58 ` [Qemu-devel] [PATCH RFC v6 5/7] migration: fix the multifd code when receiving less channels Fei Li
2018-10-30  6:05   ` Peter Xu
2018-10-30 10:05     ` Fei Li
2018-10-30 22:18       ` Peter Xu
2018-10-31 12:26         ` Fei Li
2018-10-31 13:50   ` Fei Li
2018-10-29 12:58 ` [Qemu-devel] [PATCH RFC v6 6/7] migration: fix some error handling Fei Li
2018-10-30 19:49   ` Dr. David Alan Gilbert
2018-10-31 11:25     ` Fei Li
2018-10-31 16:30       ` Dr. David Alan Gilbert
2018-11-01  5:20         ` Fei Li
2018-10-29 12:58 ` [Qemu-devel] [PATCH RFC v6 7/7] qemu_thread_create: propagate the error to callers to handle Fei Li

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=20181029125818.28720-2-fli@suse.com \
    --to=fli@suse.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=famz@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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 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.