From: patchwork-bot+netdevbpf@kernel.org
To: Zhou Qingyang <zhou1615@umn.edu>
Cc: kjlu@umn.edu, shshaikh@marvell.com, manishc@marvell.com,
GR-Linux-NIC-Dev@marvell.com, davem@davemloft.net,
kuba@kernel.org, matthias.bgg@gmail.com,
sucheta.chakraborty@qlogic.com, sritej.velaga@qlogic.com,
sony.chacko@qlogic.com, anirban.chakraborty@qlogic.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] clk: mediatek: net: qlogic: qlcnic: Fix a NULL pointer dereference in qlcnic_83xx_add_rings()
Date: Thu, 02 Dec 2021 03:00:09 +0000 [thread overview]
Message-ID: <163841400909.24500.703686292422770664.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211130110848.109026-1-zhou1615@umn.edu>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 30 Nov 2021 19:08:48 +0800 you wrote:
> In qlcnic_83xx_add_rings(), the indirect function of
> ahw->hw_ops->alloc_mbx_args will be called to allocate memory for
> cmd.req.arg, and there is a dereference of it in qlcnic_83xx_add_rings(),
> which could lead to a NULL pointer dereference on failure of the
> indirect function like qlcnic_83xx_alloc_mbx_args().
>
> Fix this bug by adding a check of alloc_mbx_args(), this patch
> imitates the logic of mbx_cmd()'s failure handling.
>
> [...]
Here is the summary with links:
- clk: mediatek: net: qlogic: qlcnic: Fix a NULL pointer dereference in qlcnic_83xx_add_rings()
https://git.kernel.org/netdev/net/c/e2dabc4f7e7b
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:[~2021-12-02 3:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 11:08 [PATCH] clk: mediatek: net: qlogic: qlcnic: Fix a NULL pointer dereference in qlcnic_83xx_add_rings() Zhou Qingyang
2021-12-02 3:00 ` 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=163841400909.24500.703686292422770664.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=anirban.chakraborty@qlogic.com \
--cc=davem@davemloft.net \
--cc=kjlu@umn.edu \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=manishc@marvell.com \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shshaikh@marvell.com \
--cc=sony.chacko@qlogic.com \
--cc=sritej.velaga@qlogic.com \
--cc=sucheta.chakraborty@qlogic.com \
--cc=zhou1615@umn.edu \
/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