linux-kernel - Re: crash in 3.12.51 (likely in 3.12.52 as well) in timer code

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <1454588837.3407.148.camel@gmail.com>
Date:	Thu, 04 Feb 2016 13:27:17 +0100
From:	Mike Galbraith <umgwanakikbuti@...il.com>
To:	Nikolay Borisov <kernel@...p.com>,
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Cc:	Jiri Slaby <jslaby@...e.cz>, Oleg Nesterov <oleg@...hat.com>,
	tglx@...utronix.de,
	SiteGround Operations <operations@...eground.com>
Subject: Re: crash in 3.12.51 (likely in 3.12.52 as well) in timer code

On Thu, 2016-02-04 at 14:21 +0200, Nikolay Borisov wrote:

> > > On a different note - is there a way to safely reproduce this so I can
> > > test the suggested fix by Thomas?
> > 
> > Hm, write a module to beat mod_delayed_work() to pulp with a NR_CPUS
> > horde, and run it in a vm where you don't care about shrapnel?
> 
> In other words, have multiple threads (NR_CPUS) that spin on
> mod_delayed_work?

Yeah, give threads lots of opportunities to collide. (not forgetting to
sleep at least occasionally;)

	-Mike