From: Theodore Ts'o <tytso@mit.edu>
To: lkp@lists.01.org
Subject: Re: [random] BUG: spinlock trylock failure on UP on CPU#0, swapper/1
Date: Sun, 15 Jun 2014 21:44:15 -0400 [thread overview]
Message-ID: <20140616014415.GA4887@thunk.org> (raw)
In-Reply-To: <539D4776.1030804@intel.com>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
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@MIT.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
WARNING: multiple messages have this Message-ID (diff)
From: "Theodore Ts'o" <tytso@mit.edu>
To: Jet Chen <jet.chen@intel.com>
Cc: Greg Price <price@mit.edu>, Fengguang Wu <fengguang.wu@intel.com>,
Yuanhan Liu <yuanhan.liu@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [random] BUG: spinlock trylock failure on UP on CPU#0, swapper/1
Date: Sun, 15 Jun 2014 21:44:15 -0400 [thread overview]
Message-ID: <20140616014415.GA4887@thunk.org> (raw)
In-Reply-To: <539D4776.1030804@intel.com>
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@MIT.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
next prev parent reply other threads:[~2014-06-16 1:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-15 7:10 [random] BUG: spinlock trylock failure on UP on CPU#0, swapper/1 Jet Chen
2014-06-15 7:12 ` Jet Chen
2014-06-16 1:44 ` Theodore Ts'o [this message]
2014-06-16 1:44 ` Theodore Ts'o
2014-06-16 1:47 ` [PATCH] random: fix nasty entropy accounting bug Theodore Ts'o
-- strict thread matches above, loose matches on Subject: below --
2014-04-05 13:38 [random] BUG: spinlock trylock failure on UP on CPU#0, swapper/1 Fengguang Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140616014415.GA4887@thunk.org \
--to=tytso@mit.edu \
--cc=lkp@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.