From: Markus Armbruster <armbru@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org,
Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Michael Roth <michael.roth@amd.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [PATCH v2 0/8] qapi: last minute improvements/changes to -compat insecure-types
Date: Mon, 02 Nov 2026 07:41:25 +0100 [thread overview]
Message-ID: <87qzh3vip6.fsf@pond.sub.org> (raw)
In-Reply-To: <20261030141713.2841710-1-berrange@redhat.com> ("Daniel P. Berrangé"'s message of "Fri, 30 Oct 2026 14:17:05 +0000")
Daniel P. Berrangé <berrange@redhat.com> writes:
> This addresses various points raised by Markus about the current
> impl/design, that would need to be addressed before this is
> included in the release.
>
> NB, the 'warn' option will repeatedly warn on every violation
> which can be somewhat unpleasant. Figuring out a mechanism to
> make it a one-time warning is an exercise for the future, given
> limited time before release.
With the doc text fix in PATCH 7, series
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Applied. Thanks!
prev parent reply other threads:[~2026-11-02 6:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 14:17 [PATCH v2 0/8] qapi: last minute improvements/changes to -compat insecure-types Daniel P. Berrangé
2026-10-30 14:17 ` [PATCH v2 1/8] qapi: make 'CompatPolicy' the first arg in compat_policy_input_ok Daniel P. Berrangé
2026-10-30 14:17 ` [PATCH v2 2/8] qapi: add 'warn' option to CompatPolicyInput Daniel P. Berrangé
2026-10-30 14:17 ` [PATCH v2 3/8] qapi: rename 'insecure-types' to 'insecure-input' Daniel P. Berrangé
2026-10-30 14:17 ` [PATCH v2 4/8] qapi: drop CompatPolicySecurity and use CompatPolicyInput Daniel P. Berrangé
2026-11-02 6:54 ` Markus Armbruster
2026-10-30 14:17 ` [PATCH v2 5/8] qapi: rename compat_policy_check_security method Daniel P. Berrangé
2026-10-30 14:17 ` [PATCH v2 6/8] qapi: reverse arg order in compat_policy_security_ok Daniel P. Berrangé
2026-10-30 14:17 ` [PATCH v2 7/8] qemu-options: document -compat insecure-input parameter Daniel P. Berrangé
2026-11-02 6:12 ` Markus Armbruster
2026-10-30 14:17 ` [PATCH v2 8/8] qapi: print a message before aborting for -compat violations Daniel P. Berrangé
2026-10-30 15:09 ` [PATCH v2 0/8] qapi: last minute improvements/changes to -compat insecure-types Marc-André Lureau
2026-11-02 6:41 ` Markus Armbruster [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=87qzh3vip6.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=pierrick.bouvier@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.