From: Jerin Jacob <jerinjacobk@gmail.com>
To: hemant.agrawal@nxp.com
Cc: Gagandeep Singh <g.singh@nxp.com>,
ferruh.yigit@amd.com, dev@dpdk.org, jerinj@marvell.com,
stable@dpdk.org
Subject: Re: [PATCH] bus/dpaa: fix outside array bounds error with GCC v13
Date: Fri, 21 Jul 2023 18:02:28 +0530 [thread overview]
Message-ID: <CALBAE1Pbi1b6jHiGJz=teE_fjoUA5QHgEcoH-OEHqv2S1Qg4xw@mail.gmail.com> (raw)
In-Reply-To: <0d101e19-a273-a4ca-9fdd-2c0262de3528@oss.nxp.com>
On Fri, Jul 21, 2023 at 4:18 PM Hemant Agrawal
<hemant.agrawal@oss.nxp.com> wrote:
>
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
>
> On 21-Jul-23 10:58 AM, Gagandeep Singh wrote:
> > Caution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, report the message using the 'Report this email' button
> >
> >
> > when RTE_ENABLE_ASSERT is enable, DPAA driver is doing
> > wrong NULL check on frame queue which allows the code
> > to have access to NULL address.
> > GCC v13 is giving array bounds error if code is
> > accessing any memory region less than 4KB.
> > This patch fixes this issue by adding proper NULL checks
> > on frame queue.
> >
> > Please refer: https://bugs.dpdk.org/show_bug.cgi?id=1233
> >
> > Bugzilla ID: 1233
> > Fixes: c47ff048b99a ("bus/dpaa: add QMAN driver core routines")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
> > ---
> > drivers/bus/dpaa/base/qbman/qman.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/bus/dpaa/base/qbman/qman.c b/drivers/bus/dpaa/base/qbman/qman.c
> > index 3949bf8712..83db0a534e 100644
> > --- a/drivers/bus/dpaa/base/qbman/qman.c
> > +++ b/drivers/bus/dpaa/base/qbman/qman.c
> > @@ -1,7 +1,7 @@
> > /* SPDX-License-Identifier: (BSD-3-Clause OR GPL-2.0)
> > *
> > * Copyright 2008-2016 Freescale Semiconductor Inc.
> > - * Copyright 2017,2019 NXP
> > + * Copyright 2017,2019-2023 NXP
> > *
> > */
> >
> > @@ -897,7 +897,7 @@ static u32 __poll_portal_slow(struct qman_portal *p, u32 is)
> > /* Lookup in the retirement table */
> > fq = table_find_fq(p,
> > be32_to_cpu(msg->fq.fqid));
> > - DPAA_BUG_ON(!fq);
> > + DPAA_BUG_ON(fq != NULL);
> > fq_state_change(p, fq, &swapped_msg, verb);
> > if (fq->cb.fqs)
> > fq->cb.fqs(p, fq, &swapped_msg);
> > @@ -909,6 +909,7 @@ static u32 __poll_portal_slow(struct qman_portal *p, u32 is)
> > #else
> > fq = (void *)(uintptr_t)msg->fq.contextB;
> > #endif
> > + DPAA_BUG_ON(fq != NULL);
> > fq_state_change(p, fq, msg, verb);
> > if (fq->cb.fqs)
> > fq->cb.fqs(p, fq, &swapped_msg);
> > --
> > 2.25.1
> >
next prev parent reply other threads:[~2023-07-21 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 5:28 Gagandeep Singh
2023-07-21 10:47 ` Hemant Agrawal
2023-07-21 12:32 ` Jerin Jacob [this message]
2023-10-04 12:28 ` David Marchand
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='CALBAE1Pbi1b6jHiGJz=teE_fjoUA5QHgEcoH-OEHqv2S1Qg4xw@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=stable@dpdk.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).