From: patchwork-bot+netdevbpf@kernel.org
To: Zhou Qingyang <zhou1615@umn.edu>
Cc: kjlu@umn.edu, sgoutham@marvell.com, lcherian@marvell.com,
gakula@marvell.com, jerinj@marvell.com, hkelam@marvell.com,
sbhatta@marvell.com, davem@davemloft.net, kuba@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] octeontx2-af: Fix a memleak bug in rvu_mbox_init()
Date: Thu, 02 Dec 2021 03:20:09 +0000 [thread overview]
Message-ID: <163841520925.978.14308206257765575112.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211130165039.192426-1-zhou1615@umn.edu>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 1 Dec 2021 00:50:39 +0800 you wrote:
> In rvu_mbox_init(), mbox_regions is not freed or passed out
> under the switch-default region, which could lead to a memory leak.
>
> Fix this bug by changing 'return err' to 'goto free_regions'.
>
> This bug was found by a static analyzer. The analysis employs
> differential checking to identify inconsistent security operations
> (e.g., checks or kfrees) between two code paths and confirms that the
> inconsistent operations are not recovered in the current function or
> the callers, so they constitute bugs.
>
> [...]
Here is the summary with links:
- octeontx2-af: Fix a memleak bug in rvu_mbox_init()
https://git.kernel.org/netdev/net/c/e07a097b4986
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:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 16:50 [PATCH] octeontx2-af: Fix a memleak bug in rvu_mbox_init() Zhou Qingyang
2021-12-02 3:20 ` 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=163841520925.978.14308206257765575112.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=kjlu@umn.edu \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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