public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, Jiri Slaby <jslaby@suse.cz>
Subject: Re: lockdep trace from kill_fasync (tty) vs account (random)
Date: Wed, 06 Mar 2013 06:19:31 -0500	[thread overview]
Message-ID: <1362568771.18799.167.camel@thor.lan> (raw)
In-Reply-To: <20130306030633.GA6567@redhat.com>

On Tue, 2013-03-05 at 22:06 -0500, Dave Jones wrote:
> Came home to this on my box that I left fuzz-testing.
> 
> [56194.899379] ======================================================
> [56194.899529] [ INFO: possible circular locking dependency detected ]
> [56194.899679] 3.9.0-rc1+ #67 Not tainted
> [56194.899769] -------------------------------------------------------
> [56194.899920] modprobe/14420 is trying to acquire lock:
> [56194.900041] blocked:  (&(&new->fa_lock)->rlock){......}, instance: ffff8800c240b4b8, at: [<ffffffff811c31d6>] kill_fasync+0x96/0x2a0
> [56194.900343] 
> but task is already holding lock:
> [56194.900478] held:     (nonblocking_pool.lock){..-...}, instance: ffffffff81ca99a0, at: [<ffffffff81417909>] account+0x39/0x1c0
> [56194.900765] 
> which lock already depends on the new lock.

Hi Dave,

Turns out it's a problem in random.

https://lkml.org/lkml/2013/3/4/295

Regards,
Peter Hurley


      reply	other threads:[~2013-03-06 11:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06  3:06 lockdep trace from kill_fasync (tty) vs account (random) Dave Jones
2013-03-06 11:19 ` Peter Hurley [this message]

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=1362568771.18799.167.camel@thor.lan \
    --to=peter@hurleysoftware.com \
    --cc=davej@redhat.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox