From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <carlos.bilbao@amd.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<linux-kernel@vger.kernel.org>, <mchan@broadcom.com>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>,
<prashant@broadcom.com>, <siva.kallam@broadcom.com>,
<kuniyu@amazon.com>
Subject: Re: [PATCH] tg3: fix array subscript out of bounds compilation error
Date: Mon, 17 Jul 2023 12:24:03 -0700 [thread overview]
Message-ID: <20230717192403.96187-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20230717143443.163732-1-carlos.bilbao@amd.com>
From: Carlos Bilbao <carlos.bilbao@amd.com>
Date: Mon, 17 Jul 2023 09:34:43 -0500
> Fix encountered compilation error in tg3.c where an array subscript was
What is the error ?
> above the array bounds of 'struct tg3_napi[5]'. Add an additional check in
> the for loop to ensure that it does not exceed the bounds of
> 'struct tg3_napi' (defined by TG3_IRQ_MAX_VECS).
>
> Reviewed-By: Carlos Bilbao <carlos.bilbao@amd.com>
> ---
> drivers/net/ethernet/broadcom/tg3.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/broadcom/tg3.c b/drivers/net/ethernet/broadcom/tg3.c
> index 4179a12fc881..33ad75b7ed91 100644
> --- a/drivers/net/ethernet/broadcom/tg3.c
> +++ b/drivers/net/ethernet/broadcom/tg3.c
> @@ -17791,7 +17791,7 @@ static int tg3_init_one(struct pci_dev *pdev,
> intmbx = MAILBOX_INTERRUPT_0 + TG3_64BIT_REG_LOW;
> rcvmbx = MAILBOX_RCVRET_CON_IDX_0 + TG3_64BIT_REG_LOW;
> sndmbx = MAILBOX_SNDHOST_PROD_IDX_0 + TG3_64BIT_REG_LOW;
> - for (i = 0; i < tp->irq_max; i++) {
> + for (i = 0; i < tp->irq_max && i < TG3_IRQ_MAX_VECS; i++) {
I'm not familiar with this driver, but it seem tg3_init_one() calls
tg3_get_invariants() before the loop and initialises irq_max as 1
or TG3_IRQ_MAX_VECS.
Where does tp->irq_max go over TG3_IRQ_MAX_VECS ?
> struct tg3_napi *tnapi = &tp->napi[i];
>
> tnapi->tp = tp;
> --
> 2.41.0
next prev parent reply other threads:[~2023-07-17 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 14:34 [PATCH] tg3: fix array subscript out of bounds compilation error Carlos Bilbao
2023-07-17 19:24 ` Kuniyuki Iwashima [this message]
2023-07-18 15:52 ` Carlos Bilbao
2023-07-19 2:54 ` Jakub Kicinski
2023-07-19 4:30 ` Eric Dumazet
2023-07-21 22:29 ` Carlos Bilbao
2023-07-22 1:17 ` Michael Chan
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=20230717192403.96187-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=carlos.bilbao@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=prashant@broadcom.com \
--cc=siva.kallam@broadcom.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).