From: Kevin Wolf <kwolf@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Fam Zheng <fam@euphon.net>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org, Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
Bandan Das <bsd@redhat.com>, Prasad J Pandit <ppandit@redhat.com>
Subject: Re: [PATCH v4] docs/secure-coding-practices: Describe how to use 'null-co' block driver
Date: Wed, 2 Jun 2021 14:29:34 +0200 [thread overview]
Message-ID: <YLd5rgHDo0lMq51S@redhat.com> (raw)
In-Reply-To: <20210601162548.2076631-1-philmd@redhat.com>
Am 01.06.2021 um 18:25 hat Philippe Mathieu-Daudé geschrieben:
> Document that security reports must use 'null-co,read-zeroes=on'
> because otherwise the memory is left uninitialized (which is an
> on-purpose performance feature).
>
> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> v4: Fixed typo (Kevin)
> v3: Simplified using Vladimir suggestion.
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2021-06-02 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 16:25 [PATCH v4] docs/secure-coding-practices: Describe how to use 'null-co' block driver Philippe Mathieu-Daudé
2021-06-02 12:29 ` 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=YLd5rgHDo0lMq51S@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=bsd@redhat.com \
--cc=fam@euphon.net \
--cc=mreitz@redhat.com \
--cc=philmd@redhat.com \
--cc=ppandit@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/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).