[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ba67020a-04bb-46b8-bc05-751684f71e8a@suswa.mountain>
Date: Tue, 2 Jul 2024 15:57:23 +0200
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Su Hui <suhui@...china.com>
Cc: arend.vanspriel@...adcom.com, kvalo@...nel.org, johannes.berg@...el.com,
kees@...nel.org, a@...repo.ru, marcan@...can.st,
quic_alokad@...cinc.com, zyytlz.wz@....com,
petr.tesarik.ext@...wei.com, duoming@....edu.cn,
colin.i.king@...il.com, frankyl@...adcom.com, meuleman@...adcom.com,
phaber@...adcom.com, linville@...driver.com,
linux-wireless@...r.kernel.org, brcm80211@...ts.linux.dev,
brcm80211-dev-list.pdl@...adcom.com, linux-kernel@...r.kernel.org,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH wireless 1/9] wifi: cfg80211: avoid garbage value of
'io_type' in brcmf_cfg80211_attach()
On Tue, Jul 02, 2024 at 08:24:44PM +0800, Su Hui wrote:
> brcmf_fil_cmd_int_get() reads the value of 'io_type' and passes it to
> brcmf_fil_cmd_data_get(). Initialize 'io_type' to avoid garbage value.
Since you're going to be resending anyway, please delete the space char
from the start of the line.
It's weird that brcmf_fil_cmd_data_get() uses the uninitialized data.
It looks like it just goes to great lengths to preserve the original
data in io_type... So it likely is harmless enough but still a strange
and complicated way write a no-op.
regards,
dan carpenter
Powered by blists - more mailing lists