From: coverity-bot <keescook@chromium.org>
To: Ryder Lee <ryder.lee@mediatek.com>
Cc: Lorenzo Bianconi <lorenzo@kernel.org>,
linux-wireless@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
Kalle Valo <kvalo@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Shayne Chen <shayne.chen@mediatek.com>,
Eric Dumazet <edumazet@google.com>,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
linux-mediatek@lists.infradead.org, Felix Fietkau <nbd@nbd.name>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org,
MeiChia Chiu <meichia.chiu@mediatek.com>,
Paolo Abeni <pabeni@redhat.com>,
Sean Wang <sean.wang@mediatek.com>,
Bo Jiao <Bo.Jiao@mediatek.com>,
Sujuan Chen <sujuan.chen@mediatek.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
linux-next@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Coverity: mt7915_rate_txpower_get(): Resource leaks
Date: Fri, 2 Dec 2022 14:26:12 -0800 [thread overview]
Message-ID: <202212021426.BE8F5215@keescook> (raw)
Hello!
This is an experimental semi-automated report about issues detected by
Coverity from a scan of next-20221202 as part of the linux-next scan project:
https://scan.coverity.com/projects/linux-next-weekly-scan
You're getting this email because you were associated with the identified
lines of code (noted below) that were touched by commits:
Thu Dec 1 17:29:14 2022 +0100
bd2404d42821 ("wifi: mt76: mt7915: add basedband Txpower info into debugfs")
Coverity reported the following:
*** CID 1527799: Resource leaks (RESOURCE_LEAK)
drivers/net/wireless/mediatek/mt76/mt7915/debugfs.c:999 in mt7915_rate_txpower_get()
993 buf = kzalloc(sz, GFP_KERNEL);
994 if (!buf)
995 return -ENOMEM;
996
997 ret = mt7915_mcu_get_txpower_sku(phy, txpwr, sizeof(txpwr));
998 if (ret)
vvv CID 1527799: Resource leaks (RESOURCE_LEAK)
vvv Variable "buf" going out of scope leaks the storage it points to.
999 return ret;
1000
1001 /* Txpower propagation path: TMAC -> TXV -> BBP */
1002 len += scnprintf(buf + len, sz - len,
1003 "\nPhy%d Tx power table (channel %d)\n",
1004 phy != &dev->phy, phy->mt76->chandef.chan->hw_value);
If this is a false positive, please let us know so we can mark it as
such, or teach the Coverity rules to be smarter. If not, please make
sure fixes get into linux-next. :) For patches fixing this, please
include these lines (but double-check the "Fixes" first):
Reported-by: coverity-bot <keescook+coverity-bot@chromium.org>
Addresses-Coverity-ID: 1527799 ("Resource leaks")
Fixes: bd2404d42821 ("wifi: mt76: mt7915: add basedband Txpower info into debugfs")
Thanks for your attention!
--
Coverity-bot
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2022-12-02 22:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202212021426.BE8F5215@keescook \
--to=keescook@chromium.org \
--cc=Bo.Jiao@mediatek.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gustavo@embeddedor.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=meichia.chiu@mediatek.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
--cc=sujuan.chen@mediatek.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).