linux-kernel - Re: [random] BUG: spinlock trylock failure on UP on CPU#0, swapper/1

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] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 15 Jun 2014 21:44:15 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Jet Chen <jet.chen@...el.com>
Cc:	Greg Price <price@....edu>, Fengguang Wu <fengguang.wu@...el.com>,
	Yuanhan Liu <yuanhan.liu@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	lkp@...org
Subject: Re: [random] BUG: spinlock trylock failure on UP on CPU#0, swapper/1

On Sun, Jun 15, 2014 at 03:12:54PM +0800, Jet Chen wrote:
> Hi Greg,
> 
> 0day kernel testing robot got the below dmesg and the first bad commit is
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> commit 0fb7a01af5b0cbe5bf365891fc4d186f2caa23f7
> Author:     Greg Price <price@....EDU>
> AuthorDate: Thu Dec 5 19:32:19 2013 -0500
>
>     random: simplify accounting code

I believe I've found the problem, thanks for the report!

There was an earlier warning when this was in the random.git tree, but
I analyzed the bug report incorrectly and thought it was due to a bug
in lib/random32.c that would only show up in testing.  My bad for not
seeing the problem earlier.

The patch will be chained to this reply and sent to LKML.

  	       	     	 	  	     - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/