From: P J P <ppandit@redhat.com>
To: Dmitry Fleytman <dmitry@daynix.com>
Cc: Qemu Developers <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Tom Victor <vv474172261@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v2] scsi: check page count while initialising descriptor rings
Date: Thu, 1 Sep 2016 10:20:20 +0530 (IST) [thread overview]
Message-ID: <alpine.LFD.2.20.1609011010550.4581@wniryva> (raw)
In-Reply-To: <8FCD84DF-B5BC-43FC-9CFB-A64E9FA81919@daynix.com>
Hello Dmitry,
+-- On Wed, 31 Aug 2016, Dmitry Fleytman wrote --+
| > - if ((ri->reqRingNumPages > PVSCSI_SETUP_RINGS_MAX_NUM_PAGES)
| > - || (ri->cmpRingNumPages > PVSCSI_SETUP_RINGS_MAX_NUM_PAGES)) {
| > - return -1;
| > - }
|
| Hello Prasad,
|
| Why did you decide to move this logic out of pvscsi_ring_init_data()?
| Why not just amend existing “if" as you did in v1 of this patch?
'ri->reqRingNumPages' and 'ri->cmpRingNumPages' values are also used in
routine 'pvscsi_dbg_dump_tx_rings_config' before 'pvscsi_ring_init_data' call.
if they were to have arbitrary values, this loop could run longer leading to
OOB memory access.
for (i = 0; i < rc->reqRingNumPages; i++) {
trace_pvscsi_tx_rings_ppn("Request Ring", rc->reqRingPPNs[i]);
}
Moving above logic to 'pvscsi_on_cmd_setup_rings' helps both functions.
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
next prev parent reply other threads:[~2016-09-01 4:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 6:49 [Qemu-devel] [PATCH v2] scsi: check page count while initialising descriptor rings P J P
2016-08-31 13:09 ` Dmitry Fleytman
2016-09-01 4:50 ` P J P [this message]
2016-09-01 7:16 ` Dmitry Fleytman
2016-09-01 11:02 ` 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=alpine.LFD.2.20.1609011010550.4581@wniryva \
--to=ppandit@redhat.com \
--cc=dmitry@daynix.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vv474172261@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).