From: Greg Kurz <groug@kaod.org>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
Markus Armbruster <armbru@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] monitor: fix dangling CPU pointer
Date: Tue, 17 Oct 2017 10:09:56 +0200 [thread overview]
Message-ID: <20171017100956.3d5c8fbe@bahia.lan> (raw)
In-Reply-To: <20171017095202.6d8a8df0@nial.brq.redhat.com>
On Tue, 17 Oct 2017 09:52:02 +0200
Igor Mammedov <imammedo@redhat.com> wrote:
> On Mon, 16 Oct 2017 20:47:56 +0200
> Greg Kurz <groug@kaod.org> wrote:
>
> ...
> > Note that the resolution should really return a CPU object, otherwise
> > we have a bug. This is achieved by relying on object_resolve_path()
> > and CPU() instead of calling object_resolve_path_type(path, TYPE_CPU).
> Did you forget to remove this part?
>
Argh yes I did... :-\ I'll send a v3 right away.
> >
> > Reported-by: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
> > Suggested-by: Igor Mammedov <imammedo@redhat.com>
> > Signed-off-by: Greg Kurz <groug@kaod.org>
> > ---
> > v2: - use object_resolve_path_type()
> > - add Reported-by tag
> > ---
> > monitor.c | 23 ++++++++++++++++++-----
> > 1 file changed, 18 insertions(+), 5 deletions(-)
> >
> > diff --git a/monitor.c b/monitor.c
> > index fe0d1bdbb461..ce577e46e568 100644
> > --- a/monitor.c
> > +++ b/monitor.c
> > @@ -200,7 +200,7 @@ struct Monitor {
> >
> > ReadLineState *rs;
> > MonitorQMP qmp;
> > - CPUState *mon_cpu;
> > + gchar *mon_cpu_path;
> > BlockCompletionFunc *password_completion_cb;
> > void *password_opaque;
> > mon_cmd_t *cmd_table;
> > @@ -579,6 +579,7 @@ static void monitor_data_init(Monitor *mon)
> >
> > static void monitor_data_destroy(Monitor *mon)
> > {
> > + g_free(mon->mon_cpu_path);
> > qemu_chr_fe_deinit(&mon->chr, false);
> > if (monitor_is_qmp(mon)) {
> > json_message_parser_destroy(&mon->qmp.parser);
> > @@ -1047,20 +1048,32 @@ int monitor_set_cpu(int cpu_index)
> > if (cpu == NULL) {
> > return -1;
> > }
> > - cur_mon->mon_cpu = cpu;
> > + g_free(cur_mon->mon_cpu_path);
> > + cur_mon->mon_cpu_path = object_get_canonical_path(OBJECT(cpu));
> > return 0;
> > }
> >
> > CPUState *mon_get_cpu(void)
> > {
> > - if (!cur_mon->mon_cpu) {
> > + CPUState *cpu;
> > +
> > + if (cur_mon->mon_cpu_path) {
> > + cpu = (CPUState *) object_resolve_path_type(cur_mon->mon_cpu_path,
> > + TYPE_CPU, NULL);
> > + if (!cpu) {
> > + g_free(cur_mon->mon_cpu_path);
> > + cur_mon->mon_cpu_path = NULL;
> > + }
> > + }
> > + if (!cur_mon->mon_cpu_path) {
> > if (!first_cpu) {
> > return NULL;
> > }
> > monitor_set_cpu(first_cpu->cpu_index);
> > + cpu = first_cpu;
> > }
> > - cpu_synchronize_state(cur_mon->mon_cpu);
> > - return cur_mon->mon_cpu;
> > + cpu_synchronize_state(cpu);
> > + return cpu;
> > }
> >
> > CPUArchState *mon_get_cpu_env(void)
> >
>
prev parent reply other threads:[~2017-10-17 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 18:47 [Qemu-devel] [PATCH v2] monitor: fix dangling CPU pointer Greg Kurz
2017-10-17 7:52 ` Igor Mammedov
2017-10-17 8:09 ` Greg Kurz [this message]
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=20171017100956.3d5c8fbe@bahia.lan \
--to=groug@kaod.org \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).