linux-kernel - Re: tip.today - scheduler bam boom crash (cpu hotplug)

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 for Android: free password hash cracker in your pocket

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

Message-ID: <1484825946.17735.7.camel@gmx.de>
Date:   Thu, 19 Jan 2017 12:39:06 +0100
From:   Mike Galbraith <efault@....de>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: tip.today - scheduler  bam boom crash (cpu hotplug)

On Thu, 2017-01-19 at 11:19 +0100, Peter Zijlstra wrote:

> OK, you also forgot to tell what you did to trigger this, but a little
> playing around seems enough to reproduce. All that was required was
> offline + online and *boom*.

Oh, sorry, it was Steven's hotplug stress script.  I thought the first
couple lines of kernel output (+$subject) told the tale.