From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: armbru@redhat.com, berrange@redhat.com, qemu-devel@nongnu.org,
qemu-block@nongnu.org, ehabkost@redhat.com
Subject: Re: [PATCH] qom: Check for wellformed id in user_creatable_add_type()
Date: Mon, 8 Mar 2021 12:17:24 +0100 [thread overview]
Message-ID: <20210308111724.GC7021@merkur.fritz.box> (raw)
In-Reply-To: <deeee390-7c4b-6857-8ec2-6d19ca8c03a0@redhat.com>
Am 06.03.2021 um 11:50 hat Paolo Bonzini geschrieben:
> On 02/03/21 18:16, Kevin Wolf wrote:
> > Most code paths for creating a user creatable object go through
> > QemuOpts, which ensures that the provided 'id' option is actually a
> > valid identifier.
> >
> > However, there are some code paths that don't go through QemuOpts:
> > qemu-storage-daemon --object (since commit 8db1efd3) and QMP object-add
> > (since it was first introduced in commit cff8b2c6). We need to have the
> > same validity check for those, too.
> >
> > This adds the check and makes it print the same error message as
> > QemuOpts on failure.
> >
> > Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> > ---
> > This makes sense even without the -object QAPIfication, so no reason to
> > wait for v3 of that series to get this fixed.
>
> It needs a check for id != NULL, but no big deal so I added it.
Oops, yes. Thanks for fixing it up.
Kevin
prev parent reply other threads:[~2021-03-08 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 17:16 [PATCH] qom: Check for wellformed id in user_creatable_add_type() Kevin Wolf
2021-03-02 19:00 ` Eric Blake
2021-03-02 19:43 ` Paolo Bonzini
2021-03-06 10:50 ` Paolo Bonzini
2021-03-08 11:17 ` Kevin Wolf [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=20210308111724.GC7021@merkur.fritz.box \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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).