[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20260121090507.3442567-1-zilin@seu.edu.cn>
Date: Wed, 21 Jan 2026 09:05:07 +0000
From: Zilin Guan <zilin@....edu.cn>
To: chunkeey@...il.com
Cc: jianhao.xu@....edu.cn,
johannes.berg@...el.com,
johannes@...solutions.net,
linux-kernel@...r.kernel.org,
linux-wireless@...r.kernel.org,
quic_rdevanat@...cinc.com,
zilin@....edu.cn
Subject: Re: [PATCH v2] wifi: p54: Fix memory leak in p54_beacon_update()
On Tue, Jan 20, 2026 at 09:25:15PM +0100, Christian Lamparter wrote:
> Ok, from what I remember, this return basically is/was and likely will be a dead-code path.
> So adding something there is only there to "look" good for the static analysis tools.
> But many commits like these have been merged before. As long as it is mentioned that
> static analysis was the reason for this. Yeah sure why not.
>
>
> Reason being why this is dead-code is that in order for the path to trigger, mac80211's
> ieee80211_beacon_get must have prepared an invalid beacon (with an invalid TIM Element)
> to start with... And looking at ieee80211_beacon_add_tim_pvb, it still looks to me like
> the IE length can't be less than 3 ever. But, I've been wrong before, if you do see please
> correct me. (If not, you don't neet to really bother with the Fixes-Tag)
>
>
> Cheers,
> Christian
Hi Christian,
Thanks for the detailed review.
I agree with your analysis. I checked the code and confirmed that mac80211
guarantees a minimum TIM length of 4 bytes for non-S1G devices.
I appreciate you accepting this patch to silence the static analysis warning.
Best regards,
Zilin Guan
Powered by blists - more mailing lists