From: Paolo Bonzini <pbonzini@redhat.com>
To: P J P <ppandit@redhat.com>
Cc: Qemu Developers <qemu-devel@nongnu.org>,
Dmitry Fleytman <dmitry@daynix.com>, Li Qiang <liqiang6-s@360.cn>
Subject: Re: [Qemu-devel] [PATCH] scsi: pvscsi: request descriptor data_length to 32 bit
Date: Mon, 5 Sep 2016 12:00:14 +0200 [thread overview]
Message-ID: <ea703469-dc33-d1f5-3221-8d0f67bde362@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1609051450510.15083@wniryva>
On 05/09/2016 11:50, P J P wrote:
> Hello Paolo, all
>
> +-- On Mon, 5 Sep 2016, Paolo Bonzini wrote --+
> | > - uint64_t data_length = r->req.dataLen;
> | > + uint32_t data_length = r->req.dataLen;
> |
> | Why is this needed if you remove the cast in MIN, below?
>
> The outer while loop below is controlled by 'data_length'. The cast in MIN
> truncates a large(64bit) value of 'data_length' to zero(0), thus setting
> 'chunk_size' to zero, which results in infinite loop as 'data_length' remains
> unchanged(> 0).
>
> Second, Removing cast below results in 'chunk_size' being set to 'sg.resid',
> for large(>32bit) values of 'data_length'. Which results in an infinite loop
> because the inner 'while(!sg.resid)' loop takes forever to read non-zero
> values into 'sg.resid'.
No, that's not what happens. chunk_size is set to sg.resid, after which:
sg.dataAddr += chunk_size;
data_length -= chunk_size;
sg.resid -= chunk_size;
The loop is reentered with sg.resid == 0, it calls into
pvscsi_get_next_sg_elem and this sets sg.resid to a nonzero value. It's
not an infinite loop.
> Above type change ensures that outer while loop is not entered if
> 'data_length' is zero. And removing cast ensures that inner while(!sg.resid)
> loop does not have run forever, ie. till large(64 bit) 'data_length' becomes
> zero.
>
> Looking at the 'vmw_pvscsi.c' Linux kernel driver, 'dataLen' seems to be set
> to an unsigned 32 bit 'bufflen' value.
The driver is irrelevant. If the data_length is an uint64_t you need to
ensure that a 64 bit buffer is processed correctly. Here you are
truncating it, which is wrong and will cause a buffer underrun.
Paolo
next prev parent reply other threads:[~2016-09-05 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 6:33 [Qemu-devel] [PATCH] scsi: pvscsi: request descriptor data_length to 32 bit P J P
2016-09-05 9:04 ` Paolo Bonzini
2016-09-05 9:50 ` P J P
2016-09-05 10:00 ` Paolo Bonzini [this message]
2016-09-05 11:13 ` P J P
2016-09-05 11:39 ` Paolo Bonzini
2016-09-05 12:58 ` P J P
2016-09-05 13:02 ` Paolo Bonzini
2016-09-05 20:52 ` P J P
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=ea703469-dc33-d1f5-3221-8d0f67bde362@redhat.com \
--to=pbonzini@redhat.com \
--cc=dmitry@daynix.com \
--cc=liqiang6-s@360.cn \
--cc=ppandit@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).