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: Tue, 4 Oct 2022 17:23:34 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Kees Cook <keescook@...omium.org> Cc: Dmitry Vyukov <dvyukov@...gle.com>, syzbot <syzbot+3a080099974c271cd7e9@...kaller.appspotmail.com>, bpf@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com, fw@...len.de, harshit.m.mogalapalli@...cle.com, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, pabeni@...hat.com, syzkaller-bugs@...glegroups.com, linux-hardening@...r.kernel.org Subject: Re: [syzbot] upstream boot error: WARNING in netlink_ack On Tue, 4 Oct 2022 17:04:00 -0700 Jakub Kicinski wrote: > > why does a fixed size mean no memset? > > Copy and paste, it seems to originate from: > > 0c19b0adb8dd ("netlink: avoid memset of 0 bytes sparse warning") > > Any idea why sparse would not like empty memsets? Google answers is. Let me test if sparse still wants the workaround.
Powered by blists - more mailing lists