linux-kernel - Re: Possible circular locking: ->mmap_sem vs jbd

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]

Message-Id: <20071016020159.5cff8976.akpm@linux-foundation.org>
Date:	Tue, 16 Oct 2007 02:01:59 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Alexey Dobriyan <adobriyan@...ru>
Cc:	linux-kernel@...r.kernel.org, a.p.zijlstra@...llo.nl, mingo@...e.hu
Subject: Re: Possible circular locking: ->mmap_sem vs jbd_handle

On Tue, 16 Oct 2007 12:54:29 +0400 Alexey Dobriyan <adobriyan@...ru> wrote:

> Got this during LTP's diotest1. Reproducable.
> 
> =======================================================
> [ INFO: possible circular locking dependency detected ]
> 2.6.23-65a6ec0d72a07f16719e9b7a96e1c4bae044b591 #2
> -------------------------------------------------------
> diotest1/13563 is trying to acquire lock:
>  (&mm->mmap_sem){----}, at: [<c107a7b7>] dio_get_page+0x4b/0x16b
> 
> but task is already holding lock:
>  (jbd_handle){--..}, at: [<c1099b05>] journal_start+0xf3/0x120
> 
> which lock already depends on the new lock.

Someone taught lockdep about journal_start?  That's gonna hurt.
-
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/