From: patchwork-bot+netdevbpf@kernel.org
To: Hui Tang <tanghui20@huawei.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
mw@semihalf.com, linux@armlinux.org.uk, leon@kernel.org,
andrew@lunn.ch, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, yusongping@huawei.com
Subject: Re: [PATCH net v5] net: mvpp2: fix possible invalid pointer dereference
Date: Sat, 19 Nov 2022 03:50:18 +0000 [thread overview]
Message-ID: <166882981818.27279.1458629384078328986.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221117084032.101144-1-tanghui20@huawei.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 17 Nov 2022 16:40:32 +0800 you wrote:
> It will cause invalid pointer dereference to priv->cm3_base behind,
> if PTR_ERR(priv->cm3_base) in mvpp2_get_sram().
>
> Fixes: a59d354208a7 ("net: mvpp2: enable global flow control")
> Signed-off-by: Hui Tang <tanghui20@huawei.com>
> ---
> v1 -> v2: patch title include target
> v2 -> v3: keep priv->cm3_base NULL if devm_ioremap_resource() failed
> v3 -> v4: change if (priv->cm3_base) to if (base)
> v4 -> v5: use the idiomatic error handling, keep success path un-indented
>
> [...]
Here is the summary with links:
- [net,v5] net: mvpp2: fix possible invalid pointer dereference
https://git.kernel.org/netdev/net/c/cbe867685386
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-11-19 3:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 8:40 Hui Tang
2022-11-19 3:50 ` patchwork-bot+netdevbpf [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=166882981818.27279.1458629384078328986.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mw@semihalf.com \
--cc=netdev@vger.kernel.org \
--cc=tanghui20@huawei.com \
--cc=yusongping@huawei.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
Powered by JetHome