From: malc <av1474@comtv.ru>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Configurable block format whitelist
Date: Tue, 27 Oct 2009 21:05:55 +0300 (MSK) [thread overview]
Message-ID: <Pine.LNX.4.64.0910272104300.2421@linmac.oyster.ru> (raw)
In-Reply-To: <m3vdi0entz.fsf@crossbow.pond.sub.org>
On Tue, 27 Oct 2009, Markus Armbruster wrote:
> We have code for a quite a few block formats. While I trust that all
> of these formats are useful at least for some people in some
> circumstances, some of them are of a kind that friends don't let
> friends use in production.
>
> This patch provides an optional block format whitelist, default off.
> If a whitelist is configured with --block-drv-whitelist, QEMU proper
> can use only whitelisted formats. Other programs, like qemu-img, are
> not affected.
>
> Drivers for formats off the whitelist still participate in format
> probing, to ensure all programs probe exactly the same. Without that,
> QEMU proper would be prone to treat images with a format off the
> whitelist as raw when the image's format is probed.
>
[..snip..]
> diff --git a/create_config b/create_config
> index 30d0487..2f052ae 100755
> --- a/create_config
> +++ b/create_config
> @@ -26,6 +26,13 @@ case $line in
> done
> echo ""
> ;;
> + CONFIG_BDRV_WHITELIST=*)
> + echo "#define CONFIG_BDRV_WHITELIST \\"
> + for drv in ${line#*=}; do
> + echo " \"${drv}\",\\"
printf ' "%s", \' ${drv}
feels less obfuscated
[..snip..]
--
mailto:av1474@comtv.ru
prev parent reply other threads:[~2009-10-27 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 17:41 [Qemu-devel] [PATCH] Configurable block format whitelist Markus Armbruster
2009-10-27 18:05 ` malc [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=Pine.LNX.4.64.0910272104300.2421@linmac.oyster.ru \
--to=av1474@comtv.ru \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.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 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).