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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 20 Mar 2022 18:17:01 +0100 From: Sebastian Gottschall <s.gottschall@...media-net.de> To: John Crispin <john@...ozen.org>, trix@...hat.com, toke@...e.dk, kvalo@...nel.org, davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com Cc: linux-wireless@...r.kernel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] ath9k: initialize arrays at compile time Am 20.03.2022 um 17:48 schrieb John Crispin: > > > On 20.03.22 16:20, trix@...hat.com wrote: >> array[size] = { 0 }; > > should this not be array[size] = { }; ?! > > If I recall correctly { 0 } will only set the first element of the > struct/array to 0 and leave random data in all others elements > > John You are right, john Sebastian
Powered by blists - more mailing lists