From: Max Reitz <mreitz@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Eric Blake <eblake@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v3 3/7] block: fix data type casting for crypto payload offset
Date: Sat, 16 Sep 2017 18:25:45 +0200 [thread overview]
Message-ID: <bfe16d45-a399-d7c3-a995-7c6d1203ab88@redhat.com> (raw)
In-Reply-To: <20170912112855.24269-4-berrange@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
On 2017-09-12 13:28, Daniel P. Berrange wrote:
> The crypto APIs report the offset of the data payload as an uint64_t
> type, but the block driver is casting to size_t or ssize_t which will
> potentially truncate.
>
> Most of the block APIs use int64_t for offsets meanwhile, so even if
> using uint64_t in the crypto block driver we are still at risk of
> truncation.
>
> Change the block crypto driver to use uint64_t, but add asserts that
> the value is less than INT64_MAX.
>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
> block/crypto.c | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
Reviewed-by: Max Reitz <mreitz@redhat.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2017-09-16 16:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 11:28 [Qemu-devel] [PATCH v3 0/7] Misc improvements to crypto block driver Daniel P. Berrange
2017-09-12 11:28 ` [Qemu-devel] [PATCH v3 1/7] block: use 1 MB bounce buffers for crypto instead of 16KB Daniel P. Berrange
2017-09-16 16:25 ` Max Reitz
2017-09-12 11:28 ` [Qemu-devel] [PATCH v3 2/7] crypto: expose encryption sector size in APIs Daniel P. Berrange
2017-09-16 16:25 ` Max Reitz
2017-09-18 13:53 ` Eric Blake
2017-09-12 11:28 ` [Qemu-devel] [PATCH v3 3/7] block: fix data type casting for crypto payload offset Daniel P. Berrange
2017-09-16 16:25 ` Max Reitz [this message]
2017-09-18 13:56 ` Eric Blake
2017-09-12 11:28 ` [Qemu-devel] [PATCH v3 4/7] block: don't use constant 512 as sector size in crypto driver Daniel P. Berrange
2017-09-16 16:24 ` Max Reitz
2017-09-18 15:02 ` Daniel P. Berrange
2017-09-18 13:57 ` Eric Blake
2017-09-12 11:28 ` [Qemu-devel] [PATCH v3 5/7] block: convert crypto driver to bdrv_co_preadv|pwritev Daniel P. Berrange
2017-09-12 12:06 ` Daniel P. Berrange
2017-09-16 16:54 ` Max Reitz
2017-09-27 12:34 ` Daniel P. Berrange
2017-09-12 11:28 ` [Qemu-devel] [PATCH v3 6/7] block: convert qcrypto_block_encrypt|decrypt to take bytes offset Daniel P. Berrange
2017-09-16 17:13 ` Max Reitz
2017-09-12 11:28 ` [Qemu-devel] [PATCH v3 7/7] block: support passthrough of BDRV_REQ_FUA in crypto driver Daniel P. Berrange
2017-09-16 17:18 ` Max Reitz
2017-09-18 14:02 ` Eric Blake
2017-09-12 11:49 ` [Qemu-devel] [PATCH v3 0/7] Misc improvements to crypto block driver no-reply
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=bfe16d45-a399-d7c3-a995-7c6d1203ab88@redhat.com \
--to=mreitz@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).