linux-kernel - Re: lockdep warning when nesting dm devices

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] [day] [month] [year] [list]

Message-Id: <1153127808.3062.0.camel@laptopd505.fenrus.org>
Date:	Mon, 17 Jul 2006 11:16:28 +0200
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Alasdair G Kergon <agk@...hat.com>
Cc:	Peter Osterlund <petero2@...ia.com>, linux-kernel@...r.kernel.org,
	dm-devel@...hat.com, Ingo Molnar <mingo@...e.hu>,
	Milan Broz <mbroz@...hat.com>,
	"Jun'ichi Nomura" <j-nomura@...jp.nec.com>
Subject: Re: lockdep warning when nesting dm devices

On Mon, 2006-07-17 at 03:45 +0100, Alasdair G Kergon wrote:
> On Sat, Jul 15, 2006 at 01:17:29PM +0200, Peter Osterlund wrote:
> > # echo "0 10000 linear /dev/loop0 0" | /sbin/dmsetup create test
> > # echo "0 10000 linear /dev/mapper/test 0" | /sbin/dmsetup create test2
>  
> > I get the following warning from the lockdep validator.
> > =============================================
> > [ INFO: possible recursive locking detected ]
> > ---------------------------------------------
> 
> Well at first sight the message is simply pointing out something expected - it
> only say "INFO" after all - viz. recursive use of
> 	down_read(&md->io_lock);

is this indeed the same io_lock? Because if it is it's a serious
deadlock; rwsem's are NOT self-recursive!
-
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/