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: Mon, 17 Oct 2022 11:54:01 +0900 From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp> To: Linus Torvalds <torvalds@...ux-foundation.org>, Yury Norov <yury.norov@...il.com>, Jakub Kicinski <kuba@...nel.org> Cc: Borislav Petkov <bp@...en8.de>, syzbot <syzbot+d0fd2bf0dd6da72496dd@...kaller.appspotmail.com>, syzkaller-bugs@...glegroups.com, Andrew Jones <ajones@...tanamicro.com>, netdev@...r.kernel.org, "David S . Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Sebastian Andrzej Siewior <bigeasy@...utronix.de>, Menglong Dong <imagedong@...cent.com>, Kuniyuki Iwashima <kuniyu@...zon.com>, Petr Machata <petrm@...dia.com>, Guo Ren <guoren@...ux.alibaba.com>, "Michael S . Tsirkin" <mst@...hat.com>, Alexander Gordeev <agordeev@...ux.ibm.com>, andriy.shevchenko@...ux.intel.com, linux@...musvillemoes.dk, caraitto@...gle.com, willemb@...gle.com, jonolson@...gle.com, amritha.nambiar@...el.com, linux-kernel@...r.kernel.org Subject: Re: [syzbot] WARNING in c_start On 2022/10/17 2:52, Linus Torvalds wrote: > Anyway, since rc1 is fairly imminent, I will just revert it for now - > I don't want to have a pending revert wait until -rc2. Thank you, Linus. Yury or Jakub, please send a revert request on commit 854701ba4c39 ("net: fix cpu_max_bits_warn() usage in netif_attrmask_next{,_and}"), for https://syzkaller.appspot.com/bug?extid=9abe5ecc348676215427 says that boot is still failing. > But I actually suspect that the thing we should really do is to just > remove the check entirely for these functions that are already defined > in terms of "if no more bits, return nr_cpu_ids". They already > basically return an error case, having them *warn* about the error > they are going to return is just obnoxious. I agree.
Powered by blists - more mailing lists