From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Daniel P . Berrange" <berrange@redhat.com>,
qemu-block@nongnu.org, "Laszlo Ersek" <lersek@redhat.com>,
qemu-devel@nongnu.org, "Gerd Hoffmann" <kraxel@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v2 1/1] hw/nvram: Always register FW_CFG_DATA_GENERATOR_INTERFACE
Date: Tue, 6 Oct 2020 14:38:54 +0200 [thread overview]
Message-ID: <20201006123854.GF4202@linux.fritz.box> (raw)
In-Reply-To: <c36178f9-67f1-2d22-6537-15c73516cbbe@redhat.com>
Am 06.10.2020 um 14:20 hat Paolo Bonzini geschrieben:
> On 06/10/20 14:15, Kevin Wolf wrote:
> > Am 06.10.2020 um 13:19 hat Philippe Mathieu-Daudé geschrieben:
> >> While the FW_CFG_DATA_GENERATOR_INTERFACE is only consumed
> >> by a device only available using system-mode (fw_cfg), it is
> >> implemented by a crypto component (tls-cipher-suites) which
> >> is always available when crypto is used.
> >>
> >> Commit 69699f3055 introduced the following error in the
> >> qemu-storage-daemon binary:
> >>
> >> $ echo -e \
> >> '{"execute": "qmp_capabilities"}\r\n{"execute": "qom-list-types"}\r\n{"execute": "quit"}\r\n' \
> >> | storage-daemon/qemu-storage-daemon --chardev stdio,id=qmp0 --monitor qmp0
> >> {"QMP": {"version": {"qemu": {"micro": 50, "minor": 1, "major": 5}, "package": ""}, "capabilities": ["oob"]}}
> >> {"return": {}}
> >> missing interface 'fw_cfg-data-generator' for object 'tls-creds'
> >> Aborted (core dumped)
> >>
> >> Since QOM dependencies are resolved at runtime, this issue
> >> could not be triggered at linktime, and we don't have test
> >> running the qemu-storage-daemon binary.
> >>
> >> Fix by always registering the QOM interface.
> >>
> >> Reported-by: Kevin Wolf <kwolf@redhat.com>
> >> Fixes: 69699f3055 ("crypto/tls-cipher-suites: Produce fw_cfg consumable blob")
> >> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> >
> > This fails to build for me:
> >
> > ../hw/nvram/meson.build:2:7: ERROR: Unknown method "add" in object.
>
> It's
>
> Based-on: <20201006111219.2300921-1-philmd@redhat.com>
>
> (which won't be applied in exactly that shape, but more or less it will
> be the same).
Oh, I see. Then I guess it's not supposed to be merged through my tree.
Kevin
next prev parent reply other threads:[~2020-10-06 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 11:19 [PATCH v2 0/1] qom: Fix missing interface in qemu-storage-daemon Philippe Mathieu-Daudé
2020-10-06 11:19 ` [PATCH v2 1/1] hw/nvram: Always register FW_CFG_DATA_GENERATOR_INTERFACE Philippe Mathieu-Daudé
2020-10-06 11:31 ` Paolo Bonzini
2020-10-06 12:15 ` Kevin Wolf
2020-10-06 12:20 ` Paolo Bonzini
2020-10-06 12:38 ` Kevin Wolf [this message]
2020-10-06 12:51 ` Paolo Bonzini
2020-10-06 12:55 ` Laszlo Ersek
2020-10-06 13:03 ` Philippe Mathieu-Daudé
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=20201006123854.GF4202@linux.fritz.box \
--to=kwolf@redhat.com \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@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).