From: MalavyaRaval <malavyaraval@gmail.com>
To: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Cc: luka.gejak@gmail.com, MalavyaRaval <malavyaraval@gmail.com>
Subject: [PATCH] staging: rtl8723bs: break long lines in rtw_sta_mgt.c
Date: Thu, 19 Mar 2026 10:42:28 -0700 [thread overview]
Message-ID: <20260319174229.62021-1-malavyaraval@gmail.com> (raw)
The original patch attempted to use the preferred sizeof(*ptr) style,
but since the target variable is a u8 pointer, this caused a buffer
overflow. Reverting to sizeof(struct sta_info) ensures the correct
allocation size while satisfying the line-splitting requirement.
Signed-off-by: MalavyaRaval <malavyaraval@gmail.com>
---
drivers/staging/rtl8723bs/core/rtw_sta_mgt.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_sta_mgt.c b/drivers/staging/rtl8723bs/core/rtw_sta_mgt.c
index 07a6db1d2317..867877413859 100644
--- a/drivers/staging/rtl8723bs/core/rtw_sta_mgt.c
+++ b/drivers/staging/rtl8723bs/core/rtw_sta_mgt.c
@@ -54,7 +54,8 @@ u32 _rtw_init_sta_priv(struct sta_priv *pstapriv)
struct sta_info *psta;
s32 i;
- pstapriv->pallocated_stainfo_buf = vzalloc(sizeof(struct sta_info) * NUM_STA + 4);
+ pstapriv->pallocated_stainfo_buf = vzalloc(sizeof(struct sta_info) *
+ NUM_STA + 4);
if (!pstapriv->pallocated_stainfo_buf)
return _FAIL;
--
2.43.0
next reply other threads:[~2026-03-19 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 17:42 MalavyaRaval [this message]
2026-03-19 18:58 ` [PATCH] staging: rtl8723bs: break long lines in rtw_sta_mgt.c Ethan Tidmore
2026-03-19 18:59 ` Ethan Tidmore
-- strict thread matches above, loose matches on Subject: below --
2026-03-19 2:48 [PATCH] staging: rtl8723bs: Break " Malavya Raval
2026-03-19 8:39 ` Luka Gejak
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=20260319174229.62021-1-malavyaraval@gmail.com \
--to=malavyaraval@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=luka.gejak@gmail.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