From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Max Reitz <mreitz@redhat.com>,
qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-img: fix regression copying secrets during convert
Date: Tue, 14 Aug 2018 13:38:22 +0100 [thread overview]
Message-ID: <20180814123822.GC24997@redhat.com> (raw)
In-Reply-To: <20180814113824.GI5025@dhcp-200-186.str.redhat.com>
On Tue, Aug 14, 2018 at 01:38:24PM +0200, Kevin Wolf wrote:
> Am 14.08.2018 um 11:35 hat Daniel P. Berrangé geschrieben:
> > When the convert command is creating an output file that needs
> > secrets, we need to ensure those secrets are passed to both the
> > blk_new_open and bdrv_create API calls.
> >
> > This is done by qemu-img extracting all opts matching the name
> > suffix "key-secret". Unfortunately the code doing this was run after the
> > call to bdrv_create(), which meant the QemuOpts it was extracting
> > secrets from was now empty.
> >
> > Previously this worked by luks as a bug meant the "key-secret"
> > parameters were not purged from the QemuOpts. This bug was fixed in
> >
> > commit b76b4f604521e59f857d6177bc55f6f2e41fd392
> > Author: Kevin Wolf <kwolf@redhat.com>
> > Date: Thu Jan 11 16:18:08 2018 +0100
> >
> > qcow2: Use visitor for options in qcow2_create()
> >
> > Exposing the latent bug in qemu-img. This fix simply moves the copying
> > of secrets to before the bdrv_create() call.
> >
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
>
> Cc: qemu-stable@nongnu.org
>
> > @@ -2461,9 +2458,9 @@ out:
> > qemu_progress_print(100, 0);
> > }
> > qemu_progress_end();
> > - qemu_opts_del(opts);
>
> Why don't we need to free opts any more?
Urgh, that's a mistake, I deleted the wrong line. v2 arriving soon....
>
> > qemu_opts_free(create_opts);
> > qemu_opts_del(sn_opts);
> > + qobject_unref(open_opts);
> > blk_unref(s.target);
> > if (s.src) {
> > for (bs_i = 0; bs_i < s.src_num; bs_i++) {
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2018-08-14 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 9:35 [Qemu-devel] [PATCH] qemu-img: fix regression copying secrets during convert Daniel P. Berrangé
2018-08-14 11:38 ` Kevin Wolf
2018-08-14 12:38 ` Daniel P. Berrangé [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=20180814123822.GC24997@redhat.com \
--to=berrange@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).