public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Jackson <mpfj-list@newflow.co.uk>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	David Woodhouse <dwmw2@infradead.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 3.10.0-rc4: jffs2: Possible circular locking dependency detected
Date: Fri, 21 Jun 2013 13:58:11 +0100	[thread overview]
Message-ID: <51C44DE3.3000202@newflow.co.uk> (raw)
In-Reply-To: <51C2FC56.1070808@newflow.co.uk>

On 20/06/13 13:57, Mark Jackson wrote:
> Just mounted a JFFS2 partition (held in NOR flash on a custom AM335x
> CPU board), and I always get the following:-
> 
> [    3.864244]
> [    3.865851] ======================================================
> [    3.872359] [ INFO: possible circular locking dependency detected ]
> [    3.878968] 3.10.0-rc4-00172-gf31c62e-dirty #249 Not tainted
> [    3.884926] -------------------------------------------------------
> [    3.891526] rcS/507 is trying to acquire lock:
> [    3.896206]  (&mm->mmap_sem){++++++}, at: [<c00b42c8>] might_fault+0x3c/0x94
> [    3.903684]
> [    3.903684] but task is already holding lock:
> [    3.909826]  (&f->sem){+.+.+.}, at: [<c016f208>] jffs2_readdir+0x40/0x1b0
> [    3.917021]
> [    3.917021] which lock already depends on the new lock.

Looks like I reported something similar earlier this year:-

http://lists.infradead.org/pipermail/linux-mtd/2013-February/045888.html

And I also found this going back to 3.0.18:-

http://www.spinics.net/lists/linux-rt-users/msg07617.html



      reply	other threads:[~2013-06-21 12:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 12:57 3.10.0-rc4: jffs2: Possible circular locking dependency detected Mark Jackson
2013-06-21 12:58 ` Mark Jackson [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=51C44DE3.3000202@newflow.co.uk \
    --to=mpfj-list@newflow.co.uk \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.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