From: Leon Romanovsky <leon@kernel.org>
To: Dan Carpenter <error27@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH net v2] net: mvneta: Fix an out of bounds check
Date: Wed, 7 Dec 2022 11:01:24 +0200 [thread overview]
Message-ID: <Y5BWZDS09uv7TTKA@unreal> (raw)
In-Reply-To: <Y5A7d1E5ccwHTYPf@kadam>
On Wed, Dec 07, 2022 at 10:06:31AM +0300, Dan Carpenter wrote:
> In an earlier commit, I added a bounds check to prevent an out of bounds
> read and a WARN(). On further discussion and consideration that check
> was probably too aggressive. Instead of returning -EINVAL, a better fix
> would be to just prevent the out of bounds read but continue the process.
>
> Background: The value of "pp->rxq_def" is a number between 0-7 by default,
> or even higher depending on the value of "rxq_number", which is a module
> parameter. If the value is more than the number of available CPUs then
> it will trigger the WARN() in cpu_max_bits_warn().
>
> Fixes: e8b4fc13900b ("net: mvneta: Prevent out of bounds read in mvneta_config_rss()")
> Signed-off-by: Dan Carpenter <error27@gmail.com>
> ---
> v2: fix the subject to say net instead of net-next.
>
> drivers/net/ethernet/marvell/mvneta.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
Thanks for the followup,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2022-12-07 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 7:06 [PATCH net v2] net: mvneta: Fix an out of bounds check Dan Carpenter
2022-12-07 9:01 ` Leon Romanovsky [this message]
2022-12-08 17:20 ` patchwork-bot+netdevbpf
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=Y5BWZDS09uv7TTKA@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thomas.petazzoni@bootlin.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 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.