From: Kevin Wolf <kwolf@redhat.com>
To: fam@euphon.net
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
"Max Reitz" <mreitz@redhat.com>
Subject: Re: [PATCH] block: Introduce zero-co:// and zero-aio://
Date: Wed, 10 Mar 2021 18:37:58 +0100 [thread overview]
Message-ID: <20210310173758.GG6076@merkur.fritz.box> (raw)
In-Reply-To: <20210310141752.5113-1-fam@euphon.net>
Am 10.03.2021 um 15:17 hat fam@euphon.net geschrieben:
> From: Fam Zheng <famzheng@amazon.com>
>
> null-co:// has a read-zeroes=off default, when used to in security
> analysis, this can cause false positives because the driver doesn't
> write to the read buffer.
>
> null-co:// has the highest possible performance as a block driver, so
> let's keep it that way. This patch introduces zero-co:// and
> zero-aio://, largely similar with null-*://, but have read-zeroes=on by
> default, so it's more suitable in cases than null-co://.
>
> Signed-off-by: Fam Zheng <fam@euphon.net>
> ---
> block/null.c | 91 ++++++++++++++++++++++++++++++++++++++++++++++++++++
If we're adding new block drivers, there should certainly be some QAPI
schema updates here.
Kevin
prev parent reply other threads:[~2021-03-10 17:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 14:17 [PATCH] block: Introduce zero-co:// and zero-aio:// fam
2021-03-10 14:22 ` Philippe Mathieu-Daudé
2021-03-10 14:28 ` Fam Zheng
2021-03-10 14:49 ` Philippe Mathieu-Daudé
2021-03-10 14:59 ` Fam Zheng
2021-03-10 14:40 ` Vladimir Sementsov-Ogievskiy
2021-03-10 14:59 ` Fam Zheng
2021-03-10 14:59 ` Max Reitz
2021-03-10 16:35 ` Fam Zheng
2021-03-11 12:11 ` Max Reitz
2021-03-10 17:37 ` 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=20210310173758.GG6076@merkur.fritz.box \
--to=kwolf@redhat.com \
--cc=fam@euphon.net \
--cc=mreitz@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).