From: Peter Xu <peterx@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] monitor: fix double-free of request error
Date: Fri, 6 Jul 2018 15:33:01 +0800 [thread overview]
Message-ID: <20180706073301.GH23001@xz-mi> (raw)
In-Reply-To: <87va9s3moa.fsf@dusky.pond.sub.org>
On Fri, Jul 06, 2018 at 08:25:57AM +0200, Markus Armbruster wrote:
> Peter Xu <peterx@redhat.com> writes:
>
> > On Thu, Jul 05, 2018 at 06:42:01PM +0200, Marc-André Lureau wrote:
> >> qmp_error_response() will free the given error. Fix double-free in
> >> later qmp_request_free().
> >>
> >> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> >
> > Reviewed-by: Peter Xu <peterx@redhat.com>
> >
> > And not related to current patch...
> >
> >> ---
> >> monitor.c | 1 +
> >> 1 file changed, 1 insertion(+)
> >>
> >> diff --git a/monitor.c b/monitor.c
> >> index 3c9c97b73f..7af1f18d13 100644
> >> --- a/monitor.c
> >> +++ b/monitor.c
> >> @@ -4186,6 +4186,7 @@ static void monitor_qmp_bh_dispatcher(void *data)
> >> } else {
> >> assert(req_obj->err);
> >> rsp = qmp_error_response(req_obj->err);
> >> + req_obj->err = NULL;
> >> monitor_qmp_respond(req_obj->mon, rsp, NULL);
> >
> > ... here not sure whether we should just pass in req_obj->id instead
> > of NULL, or maybe we can do some more assertions like:
> >
> > diff --git a/monitor.c b/monitor.c
> > index 9eb9f06599..04d2c50f4e 100644
> > --- a/monitor.c
> > +++ b/monitor.c
> > @@ -4215,10 +4215,12 @@ static void monitor_qmp_bh_dispatcher(void *data)
> >
> > mon = req_obj->mon;
> > if (req_obj->req) {
> > + assert(!req_obj->err);
>
> Makes sense.
>
> > trace_monitor_qmp_cmd_in_band(qobject_get_try_str(req_obj->id) ?: "");
> > monitor_qmp_dispatch(mon, req_obj->req, req_obj->id);
> > } else {
> > assert(req_obj->err);
> > + assert(!req_obj->id);
>
> I'd simply pass req_obj->id to monitor_qmp_respond(). Yes, it'll always
> be null, but the code would do the right thing if that should ever
> change.
Agreed.
>
> > rsp = qmp_error_response(req_obj->err);
> > monitor_qmp_respond(mon, rsp, NULL);
> > qobject_unref(rsp);
> >
> > Thanks,
>
> Perhaps even reorder to put the error case first:
>
> if (req_obj->err) {
> assert(!req_obj->req);
> rsp = qmp_error_response(req_obj->err);
> req_obj->err = NULL;
> monitor_qmp_respond(req_obj->mon, rsp, req_obj->id);
> qobject_unref(rsp);
> } else if (req_obj->req) {
> trace_monitor_qmp_cmd_in_band(qobject_get_try_str(req_obj->id) ?: "");
> monitor_qmp_dispatch(req_obj->mon, req_obj->req, req_obj->id);
> }
>
> Matter of taste.
Looks good to me. Thanks,
--
Peter Xu
next prev parent reply other threads:[~2018-07-06 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 16:42 [Qemu-devel] [PATCH] monitor: fix double-free of request error Marc-André Lureau
2018-07-06 4:06 ` Peter Xu
2018-07-06 6:25 ` Markus Armbruster
2018-07-06 7:33 ` Peter Xu [this message]
2018-07-06 6:00 ` Markus Armbruster
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=20180706073301.GH23001@xz-mi \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=marcandre.lureau@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).