From: coverity-bot <keescook@chromium.org>
To: Sean Wang <sean.wang@mediatek.com>
Cc: YN Chen <YN.Chen@mediatek.com>,
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>,
Leon Yen <leon.yen@mediatek.com>,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
Deren Wu <deren.wu@mediatek.com>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Johannes Berg <johannes.berg@intel.com>,
Quan Zhou <quan.zhou@mediatek.com>,
linux-mediatek@lists.infradead.org, Felix Fietkau <nbd@nbd.name>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Ben Greear <greearb@candelatech.com>,
Ming Yen Hsieh <mingyen.hsieh@mediatek.com>,
Ryder Lee <ryder.lee@mediatek.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
linux-next@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Coverity: mt7921_check_offload_capability(): Resource leaks
Date: Fri, 2 Dec 2022 14:21:46 -0800 [thread overview]
Message-ID: <202212021421.6B6D4F45@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:13 2022 +0100
034ae28b56f1 ("wifi: mt76: mt7921: introduce remain_on_channel support")
Coverity reported the following:
*** CID 1527806: Resource leaks (RESOURCE_LEAK)
drivers/net/wireless/mediatek/mt76/mt7921/init.c:178 in mt7921_check_offload_capability()
172 ret = request_firmware(&fw, fw_wm, dev);
173 if (ret)
174 return ret;
175
176 if (!fw || !fw->data || fw->size < sizeof(*hdr)) {
177 dev_err(dev, "Invalid firmware\n");
vvv CID 1527806: Resource leaks (RESOURCE_LEAK)
vvv Variable "fw" going out of scope leaks the storage it points to.
178 return -EINVAL;
179 }
180
181 data = fw->data;
182 hdr = (const void *)(fw->data + fw->size - sizeof(*hdr));
183
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: 1527806 ("Resource leaks")
Fixes: 034ae28b56f1 ("wifi: mt76: mt7921: introduce remain_on_channel support")
Thanks for your attention!
--
Coverity-bot
WARNING: multiple messages have this Message-ID (diff)
From: coverity-bot <keescook@chromium.org>
To: Sean Wang <sean.wang@mediatek.com>
Cc: YN Chen <YN.Chen@mediatek.com>,
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>,
Leon Yen <leon.yen@mediatek.com>,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
Deren Wu <deren.wu@mediatek.com>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Johannes Berg <johannes.berg@intel.com>,
Quan Zhou <quan.zhou@mediatek.com>,
linux-mediatek@lists.infradead.org, Felix Fietkau <nbd@nbd.name>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Ben Greear <greearb@candelatech.com>,
Ming Yen Hsieh <mingyen.hsieh@mediatek.com>,
Ryder Lee <ryder.lee@mediatek.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
linux-next@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Coverity: mt7921_check_offload_capability(): Resource leaks
Date: Fri, 2 Dec 2022 14:21:46 -0800 [thread overview]
Message-ID: <202212021421.6B6D4F45@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:13 2022 +0100
034ae28b56f1 ("wifi: mt76: mt7921: introduce remain_on_channel support")
Coverity reported the following:
*** CID 1527806: Resource leaks (RESOURCE_LEAK)
drivers/net/wireless/mediatek/mt76/mt7921/init.c:178 in mt7921_check_offload_capability()
172 ret = request_firmware(&fw, fw_wm, dev);
173 if (ret)
174 return ret;
175
176 if (!fw || !fw->data || fw->size < sizeof(*hdr)) {
177 dev_err(dev, "Invalid firmware\n");
vvv CID 1527806: Resource leaks (RESOURCE_LEAK)
vvv Variable "fw" going out of scope leaks the storage it points to.
178 return -EINVAL;
179 }
180
181 data = fw->data;
182 hdr = (const void *)(fw->data + fw->size - sizeof(*hdr));
183
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: 1527806 ("Resource leaks")
Fixes: 034ae28b56f1 ("wifi: mt76: mt7921: introduce remain_on_channel support")
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
next reply other threads:[~2022-12-02 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 22:21 coverity-bot [this message]
2022-12-02 22:21 ` Coverity: mt7921_check_offload_capability(): Resource leaks coverity-bot
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=202212021421.6B6D4F45@keescook \
--to=keescook@chromium.org \
--cc=YN.Chen@mediatek.com \
--cc=davem@davemloft.net \
--cc=deren.wu@mediatek.com \
--cc=edumazet@google.com \
--cc=greearb@candelatech.com \
--cc=gustavo@embeddedor.com \
--cc=johannes.berg@intel.com \
--cc=kai.heng.feng@canonical.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=leon.yen@mediatek.com \
--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=mingyen.hsieh@mediatek.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quan.zhou@mediatek.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.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 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.