qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fan Ni <fan.ni@samsung.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: "Michael Tokarev" <mjt@tls.msk.ru>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Michael Tsirkin" <mst@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"linuxarm@huawei.com" <linuxarm@huawei.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Yuquan Wang" <wangyuquan1236@phytium.com.cn>
Subject: Re: [PATCH 1/3] hw/cxl: Fix out of bound array access
Date: Mon, 18 Sep 2023 16:11:12 +0000	[thread overview]
Message-ID: <20230918161104.GA3330304@sjcvldevvm72> (raw)
In-Reply-To: <20230918150259.11165-2-Jonathan.Cameron@huawei.com>

On Mon, Sep 18, 2023 at 04:02:57PM +0100, Jonathan Cameron wrote:

> From: Dmitry Frolov <frolov@swemel.ru>
> 
> According to cxl_interleave_ways_enc(), fw->num_targets is allowed to be up
> to 16. This also corresponds to CXL r3.0 spec. So, the fw->target_hbs[]
> array is iterated from 0 to 15. But it is staticaly declared of length 8.

s/staticaly/statically/

Fan
> Thus, out of bound array access may occur.
> 
> Fixes: c28db9e000 ("hw/pci-bridge: Make PCIe and CXL PXB Devices inherit from TYPE_PXB_DEV")
> Signed-off-by: Dmitry Frolov <frolov@swemel.ru>
> Reviewed-by: Michael Tokarev <mjt@tls.msk.ru>
> Link: https://urldefense.com/v3/__https://lore.kernel.org/r/20230913101055.754709-1-frolov@swemel.ru__;!!EwVzqGoTKBqv-0DWAJBm!RYOYJeMCX_mlzCETIKjHDYun2TZCQxC7wF1SxIdUwJ3BYbDOtmDpTaVXXiQgiFwLYI_4JAnU6Asem4T0aHKzwzPJWer7$ 
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
>  include/hw/cxl/cxl.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/hw/cxl/cxl.h b/include/hw/cxl/cxl.h
> index 56c9e7676e..4944725849 100644
> --- a/include/hw/cxl/cxl.h
> +++ b/include/hw/cxl/cxl.h
> @@ -29,7 +29,7 @@ typedef struct PXBCXLDev PXBCXLDev;
>  typedef struct CXLFixedWindow {
>      uint64_t size;
>      char **targets;
> -    PXBCXLDev *target_hbs[8];
> +    PXBCXLDev *target_hbs[16];
>      uint8_t num_targets;
>      uint8_t enc_int_ways;
>      uint8_t enc_int_gran;
> -- 
> 2.39.2
> 

  reply	other threads:[~2023-09-18 16:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 15:02 [PATCH 0/3] hw/cxl: Misc small fixes Jonathan Cameron via
2023-09-18 15:02 ` [PATCH 1/3] hw/cxl: Fix out of bound array access Jonathan Cameron via
2023-09-18 16:11   ` Fan Ni [this message]
2023-09-18 15:02 ` [PATCH 2/3] hw/mem/cxl_type3: Add missing copyright and license notice Jonathan Cameron via
2023-09-18 16:12   ` Fan Ni
2023-09-18 16:31   ` Peter Maydell
2023-09-18 17:00     ` Jonathan Cameron via
2023-09-18 17:26       ` Dave Jiang
2023-09-18 17:38         ` Peter Maydell
2023-09-19  9:35           ` Jonathan Cameron via
2023-09-18 18:17       ` Dave Jiang
2023-09-18 21:14       ` Ira Weiny
2023-09-19  8:47         ` Daniel P. Berrangé
2023-09-19 10:00           ` Jonathan Cameron via
2023-09-18 21:21   ` Warner Losh
2023-09-18 15:02 ` [PATCH 3/3] docs/cxl: Cleanout some more aarch64 examples Jonathan Cameron via
2023-09-18 16:13   ` Fan Ni
2023-09-18 16:35   ` Peter Maydell

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=20230918161104.GA3330304@sjcvldevvm72 \
    --to=fan.ni@samsung.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=linuxarm@huawei.com \
    --cc=mjt@tls.msk.ru \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=wangyuquan1236@phytium.com.cn \
    /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).