From: Alexander Graf <agraf@suse.de>
To: P J P <ppandit@redhat.com>, Qemu Developers <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, Li Qiang <liqiang6-s@360.cn>,
Hannes Reinecke <hare@suse.de>,
Prasad J Pandit <pjp@fedoraproject.org>
Subject: Re: [Qemu-devel] [PATCH v2] scsi: megasas: check 'read_queue_head' index value
Date: Wed, 25 May 2016 14:30:35 +0200 [thread overview]
Message-ID: <57459AEB.1080208@suse.de> (raw)
In-Reply-To: <1464179110-18593-1-git-send-email-ppandit@redhat.com>
On 05/25/2016 02:25 PM, P J P wrote:
> From: Prasad J Pandit <pjp@fedoraproject.org>
>
> While doing MegaRAID SAS controller command frame lookup, routine
> 'megasas_lookup_frame' uses 'read_queue_head' value as an index
> into 'frames[MEGASAS_MAX_FRAMES=2048]' array. Limit its value
> within array bounds to avoid any OOB access.
>
> Reported-by: Li Qiang <liqiang6-s@360.cn>
> Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
Reviewed-by: Alexander Graf <agraf@suse.de>
Alex
> ---
> hw/scsi/megasas.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> Update as per
> -> https://lists.gnu.org/archive/html/qemu-devel/2016-05/msg04403.html
>
> diff --git a/hw/scsi/megasas.c b/hw/scsi/megasas.c
> index bf642d4..cc66d36 100644
> --- a/hw/scsi/megasas.c
> +++ b/hw/scsi/megasas.c
> @@ -650,7 +650,9 @@ static int megasas_init_firmware(MegasasState *s, MegasasCmd *cmd)
> pa_hi = le32_to_cpu(initq->pi_addr_hi);
> s->producer_pa = ((uint64_t) pa_hi << 32) | pa_lo;
> s->reply_queue_head = ldl_le_pci_dma(pcid, s->producer_pa);
> + s->reply_queue_head %= MEGASAS_MAX_FRAMES;
> s->reply_queue_tail = ldl_le_pci_dma(pcid, s->consumer_pa);
> + s->reply_queue_tail %= MEGASAS_MAX_FRAMES;
> flags = le32_to_cpu(initq->flags);
> if (flags & MFI_QUEUE_FLAG_CONTEXT64) {
> s->flags |= MEGASAS_MASK_USE_QUEUE64;
prev parent reply other threads:[~2016-05-25 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 12:25 [Qemu-devel] [PATCH v2] scsi: megasas: check 'read_queue_head' index value P J P
2016-05-25 12:30 ` Alexander Graf [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=57459AEB.1080208@suse.de \
--to=agraf@suse.de \
--cc=hare@suse.de \
--cc=liqiang6-s@360.cn \
--cc=pbonzini@redhat.com \
--cc=pjp@fedoraproject.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.