linux-kernel - Re: [PATCH] staging: rtl8723bs: refactor BSS Coexistence channel report logic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMbZB6PiT5KSLU43pPMoobVFz5dGhXyS5Lf1e6UBDpDbpz0FvA@mail.gmail.com>
Date: Thu, 29 Jan 2026 00:05:51 -0800
From: Te-Hsiu Huang <tehsiu.huang@...il.com>
To: Dan Carpenter <dan.carpenter@...aro.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Joe Perches <joe@...ches.com>, 
	linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: refactor BSS Coexistence channel
 report logic

>
> We only ever set the first element in the class_active[] array.
> #puzzled
>
> > +     bool ch_present[BSS_COEX_MAX_CLASSES][BSS_COEX_MAX_CHANNELS] = {{false}};
>
> Btw, use "= {};" to initialize arrays to zero.  It's not standard C, but
> it's kernel C.
>
> regards,
> dan carpenter
>

Hi Dan,
Thanks for your time!! I understand the confusion. I kept the array
structure because it reflects the IEEE 802.11 Intolerant Channel
Report format, which is organized by Regulatory Classes.

Although the driver currently only reports for the 2.4GHz class (index
0), using an array makes the code semantically aligned with the
specification and easier to extend when other operating classes need
to be supported in the future.

I have submitted a V2 which uses the '= {}' initialization you suggested.