linux-kernel - Re: mq: INFO: possible circular locking dependency detected

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: <20120807063955.GX23464@ZenIV.linux.org.uk>
Date:	Tue, 7 Aug 2012 07:39:55 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Fengguang Wu <fengguang.wu@...el.com>
Cc:	Sasha Levin <levinsasha928@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Dave Jones <davej@...hat.com>,
	Kamal Mostafa <kamal@...onical.com>,
	"Peter M. Petrakis" <peter.petrakis@...onical.com>,
	Dann Frazier <dann.frazier@...onical.com>,
	Massimo Morana <massimo.morana@...onical.com>,
	Jan Kara <jack@...e.cz>, linux-fsdevel@...r.kernel.org
Subject: Re: mq: INFO: possible circular locking dependency detected

On Tue, Aug 07, 2012 at 01:04:12PM +0800, Fengguang Wu wrote:

> FYI, here is a different back trace on that commit.
> 
> [    3.255043] ======================================================
> [    3.255052] [ INFO: possible circular locking dependency detected ]
> [    3.255052] 3.5.0-rc6-bisect-00355-geb04c28 #4 Not tainted         
> [    3.255052] -------------------------------------------------------
> [    3.255052] init/1 is trying to acquire lock:
> [    3.255052]  (&mm->mmap_sem){++++++}, at: [<ffffffff81180d00>] might_fault+0x70/0xe0
> [    3.255052]
> [    3.255052] but task is already holding lock:
> [    3.255052]  (&sb->s_type->i_mutex_key){+.+.+.}, at: [<ffffffff811d191e>] vfs_readdir+0x6e/0x130

Do you see any similar with the _next_ commit?
--
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/