From: Ping-Ke Shih <pkshih@realtek.com>
To: Abdurrahman Karadag <abdurrahmankaradag19@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"kvalo@kernel.org" <kvalo@kernel.org>,
"briannorris@chromium.org" <briannorris@chromium.org>
Subject: RE: [PATCH v2 wireless] wifi: rtw88: debugfs: don't vzalloc(0) when rsvd_page is read unconfigured
Date: Fri, 28 Aug 2026 00:42:02 +0000 [thread overview]
Message-ID: <bd7176af6556460882d032f7da593d6f@realtek.com> (raw)
In-Reply-To: <20260827131244.35623-1-abdurrahmankaradag19@gmail.com>
Abdurrahman Karadag <abdurrahmankaradag19@gmail.com> wrote:
> Reading the rsvd_page debugfs entry before writing a page offset and
> count to it calls vzalloc() with a size of zero, because
> rsvd_page.page_num defaults to 0. vmalloc warns about this:
>
> WARNING: mm/vmalloc.c:4019 at __vmalloc_node_range_noprof+0x9ac/0xa30
> ...
> Call Trace:
> __vmalloc_node_noprof+0x4c/0x70
> rtw_debugfs_get_rsvd_page+0x4c/0x110 [rtw88_core]
> seq_read_iter+0x132/0x4b0
> seq_read+0x12e/0x1c0
> full_proxy_read+0x6f/0xc0
> vfs_read+0xdd/0x490
>
> rtw_fw_dump_fifo() would reject the zero size anyway, but only after
> the allocation. Check for a zero buffer size first and print a short
> usage hint instead of allocating.
>
> Fixes: e3037485c68e ("rtw88: new Realtek 802.11ac driver")
> Signed-off-by: Abdurrahman Karadag <abdurrahmankaradag19@gmail.com>
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
> ---
> v2: no code change. Add the wireless target tree to the subject and Cc
> the maintainers/blamed authors that v1 missed.
Actually, target tree of Realtek Wifi driver should be rtw-next or rtw.
[1] https://github.com/pkshih/rtw.git rtw-next
next prev parent reply other threads:[~2026-08-28 0:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 12:48 [PATCH] wifi: rtw88: debugfs: don't vzalloc(0) when rsvd_page is read unconfigured Abdurrahman Karadag
2026-08-27 13:12 ` [PATCH v2 wireless] " Abdurrahman Karadag
2026-08-28 0:42 ` Ping-Ke Shih [this message]
[not found] ` <CA+tD5P_CN_g6eFzbYW9AvgCDZ8z4dieahFAOScXssC_HY1XDOg@mail.gmail.com>
2026-08-28 9:31 ` Ping-Ke Shih
2026-09-02 3:51 ` 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=bd7176af6556460882d032f7da593d6f@realtek.com \
--to=pkshih@realtek.com \
--cc=abdurrahmankaradag19@gmail.com \
--cc=briannorris@chromium.org \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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.