From: Hongling Zeng <zhongling0719@126.com>
To: Sean Wang <sean.wang@kernel.org>,
Hongling Zeng <zenghongling@kylinos.cn>
Cc: nbd@nbd.name, lorenzo@kernel.org, ryder.lee@mediatek.com,
shayne.chen@mediatek.com, sean.wang@mediatek.com,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
xiong.huang@mediatek.com, madhurkumar004@gmail.com,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2] wifi: mt76: mt7921: fix resource leak in probe error path
Date: Wed, 27 May 2026 13:35:12 +0800 [thread overview]
Message-ID: <6A168290.1030507@126.com> (raw)
In-Reply-To: <CAGp9LzruaD57tE5XHHAM8mKoPc-JQSAcaTdgvdSfESJjz-9XnA@mail.gmail.com>
Hi Sean,
Thanks for the review! You're absolutely right about the incorrect
Fixes: tag.
Here's v3 with the correct Fixes tags pointing to the actual commits that
introduced the resource leaks:
- ee5bb35d2b83 introduced the pcim_iomap_region() direct return
- 222606f43b58 introduced the devm_kmemdup() direct return
Thanks again for catching that.
Regards,
Hongling
在 2026年05月27日 12:48, Sean Wang 写道:
> Hi,
>
> On Tue, May 26, 2026 at 10:44 PM Hongling Zeng <zenghongling@kylinos.cn> wrote:
>> When pcim_iomap_region() or devm_kmemdup() fail, the code returns
>> directly without cleaning up previously allocated resources:
>> - mt76_device allocated by mt76_alloc_device()
>> - pci irq vectors allocated by pci_alloc_irq_vectors()
>> Fix this by jumping to the existing error cleanup path instead of
>> returning directly.
>>
>> To avoid using an uninitialized variable in the error path, move the
>> dev initialization before the error checks.
>>
>> Fixes: 234738ea3390 ("phy: ti-pipe3: move clk initialization to a separate function")
>> Signed-off-by: Hongling Zeng <zenghongling@kylinos.cn>
>>
> The code change itself looks correct, but commit message Fixes: tag is wrong.
>
> It points to 234738ea3390 ("phy: ti-pipe3: move clk initialization to
> a separate function"), which is unrelated to mt76/mt7921.
>
> The two direct-return leaks appear to come from:
> - ee5bb35d2b83 ("wifi: mt76: mt7921: Replace deprecated PCI
> function") for the pcim_iomap_region() path.
> - 222606f43b58 ("wifi: mt76: mt7921: handle MT7902 irq_map quirk
> with mutable copy") for the MT7902 devm_kmemdup() path.
>
>> ---
>> Change in v1
>> --fix uninitialized variable warning
>> ---
>> drivers/net/wireless/mediatek/mt76/mt7921/pci.c | 15 ++++++++++-----
>> 1 file changed, 10 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/net/wireless/mediatek/mt76/mt7921/pci.c b/drivers/net/wireless/mediatek/mt76/mt7921/pci.c
>> index 7a790ddf43bb..49a37185f056 100644
>> --- a/drivers/net/wireless/mediatek/mt76/mt7921/pci.c
>> +++ b/drivers/net/wireless/mediatek/mt76/mt7921/pci.c
>> @@ -343,11 +343,14 @@ static int mt7921_pci_probe(struct pci_dev *pdev,
>>
>> pci_set_drvdata(pdev, mdev);
>>
>> + dev = container_of(mdev, struct mt792x_dev, mt76);
>> +
>> regs = pcim_iomap_region(pdev, 0, pci_name(pdev));
>> - if (IS_ERR(regs))
>> - return PTR_ERR(regs);
>> + if (IS_ERR(regs)) {
>> + ret = PTR_ERR(regs);
>> + goto err_free_dev;
>> + }
>>
>> - dev = container_of(mdev, struct mt792x_dev, mt76);
>> dev->fw_features = features;
>> dev->hif_ops = &mt7921_pcie_ops;
>> dev->irq_map = &irq_map;
>> @@ -359,8 +362,10 @@ static int mt7921_pci_probe(struct pci_dev *pdev,
>> /* MT7902 needs a mutable copy because wm2_complete_mask differs */
>> map = devm_kmemdup(&pdev->dev, &irq_map,
>> sizeof(irq_map), GFP_KERNEL);
>> - if (!map)
>> - return -ENOMEM;
>> + if (!map) {
>> + ret = -ENOMEM;
>> + goto err_free_dev;
>> + }
>>
>> map->rx.wm2_complete_mask = 0;
>> dev->irq_map = map;
>> --
>> 2.25.1
>>
>>
prev parent reply other threads:[~2026-05-27 5:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 3:43 [PATCH v2] wifi: mt76: mt7921: fix resource leak in probe error path Hongling Zeng
2026-05-27 4:48 ` Sean Wang
2026-05-27 5:35 ` Hongling Zeng [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=6A168290.1030507@126.com \
--to=zhongling0719@126.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=madhurkumar004@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
--cc=xiong.huang@mediatek.com \
--cc=zenghongling@kylinos.cn \
/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