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
| ||
|
Date: Wed, 1 Nov 2017 09:45:25 +0100 From: Peter Zijlstra <peterz@...radead.org> To: syzbot <bot+2af19c9e1ffe4d4ee1d16c56ae7580feaee75765@...kaller.appspotmail.com> Cc: dvhart@...radead.org, linux-kernel@...r.kernel.org, mingo@...hat.com, syzkaller-bugs@...glegroups.com, tglx@...utronix.de Subject: Re: WARNING in get_pi_state On Tue, Oct 31, 2017 at 11:38:12AM +0100, Peter Zijlstra wrote: > On Tue, Oct 31, 2017 at 11:31:34AM +0100, Peter Zijlstra wrote: > > > And of course, now it went *splat*, lemme continue staring.. > > PEBKAC, turns out I was running the kernel without the patch in, and it > only took 3100 seconds to trigger the splat.. > > I am now actually running the kernel with the patch in, I'll leave the > machine running it for a few hours. OK, I let the kernel+patch run over night and it still lives. That's almost 22 hours of running the repro without issue.
Powered by blists - more mailing lists