linux-kernel - Re: Fwd: [bug] as_merged_requests(): possible recursive locking 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>] [day] [month] [year] [list]

Message-Id: <1201866822.12473.6.camel@nikanth-laptop.blr.novell.com>
Date:	Fri, 01 Feb 2008 17:23:42 +0530
From:	Nikanth Karthikesan <knikanth@...e.de>
To:	Jens Axboe <jens.axboe@...cle.com>, Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Fwd: [bug] as_merged_requests(): possible recursive locking
	detected

> > am i right that lockdep complained about real lockup potential here?
> > (i.e. it caught a real bug) So there's no need to change anything on the
> > lockdep side, right?
> 
> Right, no bug in lockdep, the locking code and swap_io_context() are
> just screwed up.
> 

I doubt a bug in lockdep. Here we just swap the pointers but use the
addresses themselves to order locks. And we do not change the
contents(lock) in those addresses. So it could be a lockdep bug.

Thanks
Nikanth Karthikesan



--
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/