From: Zong-Zhe Yang <kevin_yang@realtek.com>
To: Ping-Ke Shih <pkshih@realtek.com>, Zilin Guan <zilin@seu.edu.cn>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jianhao.xu@seu.edu.cn" <jianhao.xu@seu.edu.cn>
Subject: RE: [PATCH v2] wifi: rtw89: debug: Fix memory leak in __print_txpwr_map()
Date: Tue, 20 Jan 2026 03:39:01 +0000 [thread overview]
Message-ID: <e0ddcb2d043c4006bc34a039f7469e04@realtek.com> (raw)
In-Reply-To: <1127a2bb3b86437e82cf4b46c1a73f44@realtek.com>
Ping-Ke Shih <pkshih@realtek.com> wrote:
> Zong-Zhe Yang <kevin_yang@realtek.com> wrote:
> > Zilin Guan <zilin@seu.edu.cn> wrote:
> > >
> > > In __print_txpwr_map(), memory is allocated to bufp via vzalloc().
> > > If max_valid_addr is 0, the function returns -EOPNOTSUPP immediately
> > > without freeing bufp, leading to a memory leak.
> > >
> > > Since the validation of max_valid_addr does not depend on the allocated
> > > memory, fix this by moving the vzalloc() call after the check.
> > >
> > > Compile tested only. Issue found using a prototype static analysis tool
> > > and code review.
> > >
> > > Fixes: 036042e15770 ("wifi: rtw89: debug: txpwr table supports Wi-Fi 7 chips")
> > > Suggested-by: Zong-Zhe Yang <kevin_yang@realtek.com>
> > > Signed-off-by: Zilin Guan <zilin@seu.edu.cn>
> > > ---
> > > Changes in v2:
> > > - Move memory allocation after validation check to avoid leak.
> > >
> > > drivers/net/wireless/realtek/rtw89/debug.c | 8 ++++----
> > > 1 file changed, 4 insertions(+), 4 deletions(-)
> > >
> > > diff --git a/drivers/net/wireless/realtek/rtw89/debug.c
> > > b/drivers/net/wireless/realtek/rtw89/debug.c
> > > index 1264c2f82600..987eef8170f2 100644
> > > --- a/drivers/net/wireless/realtek/rtw89/debug.c
> > > +++ b/drivers/net/wireless/realtek/rtw89/debug.c
> > > @@ -825,10 +825,6 @@ static ssize_t __print_txpwr_map(struct rtw89_dev *rtwdev,
> char
> > > *buf, size_t buf
> > > s8 *bufp, tmp;
> > > int ret;
> > >
> > > - bufp = vzalloc(map->addr_to - map->addr_from + 4);
> > > - if (!bufp)
> > > - return -ENOMEM;
> > > -
> > > if (path_num == 1)
> > > max_valid_addr = map->addr_to_1ss;
> > > else
> > > @@ -837,6 +833,10 @@ static ssize_t __print_txpwr_map(struct rtw89_dev *rtwdev,
> char
> > > *buf, size_t buf
> > > if (max_valid_addr == 0)
> > > return -EOPNOTSUPP;
> > >
> > > + bufp = vzalloc(map->addr_to - map->addr_from + 4);
> > > + if (!bufp)
> > > + return -ENOMEM;
> > > +
> > > for (addr = map->addr_from; addr <= max_valid_addr; addr += 4) {
> > > ret = rtw89_mac_txpwr_read32(rtwdev, RTW89_PHY_0, addr, &val);
> > > if (ret)
> > > --
> > > 2.34.1
> >
> > Looks good to me.
>
> I suppose I can add
> Reviewed-by: Zong-Zhe Yang <kevin_yang@realtek.com>
>
> Okay?
Okay, thanks.
next prev parent reply other threads:[~2026-01-20 3:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 13:08 [PATCH v2] wifi: rtw89: debug: Fix memory leak in __print_txpwr_map() Zilin Guan
2026-01-20 3:27 ` Zong-Zhe Yang
2026-01-20 3:31 ` Ping-Ke Shih
2026-01-20 3:39 ` Zong-Zhe Yang [this message]
2026-01-22 2:02 ` Ping-Ke Shih
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=e0ddcb2d043c4006bc34a039f7469e04@realtek.com \
--to=kevin_yang@realtek.com \
--cc=jianhao.xu@seu.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=zilin@seu.edu.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