linux-kernel - Re: 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20061016084255.10f133b6.rdunlap@xenotime.net>
Date:	Mon, 16 Oct 2006 08:42:55 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Nick Piggin <nickpiggin@...oo.com.au>
Cc:	"alpha @ steudten Engineering" <alpha@...udten.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: INFO: possible circular locking dependency detected

On Tue, 17 Oct 2006 00:32:44 +1000 Nick Piggin wrote:

> alpha @ steudten Engineering wrote:
> > =======================================================
> > [ INFO: possible circular locking dependency detected ]
> > 2.6.18-1.2189self #1
> > -------------------------------------------------------
> > kswapd0/186 is trying to acquire lock:
> >  (&inode->i_mutex){--..}, at: [<c0326e32>] mutex_lock+0x21/0x24
> > 
> > but task is already holding lock:
> >  (iprune_mutex){--..}, at: [<c0326e32>] mutex_lock+0x21/0x24
> > 
> > which lock already depends on the new lock.
> 
> Thanks. __grab_cache_page wants to clear __GFP_FS, because it is
> holding the i_mutex so we don't want to reenter the filesystem in
> page reclaim.
> 
> This would be an easy two liner, except those funny page_cache_alloc
> routines which take a mapping rather than a gfp_t argument :P

and it would be only one email, but you forgot spaces there,
so it's too ugly to use.  ;)  i.e., please add spaces around
the '&'.

and it's an attachment :(

> Anyway, I'll get around to writing the real patch and queue it up
> with my other buffered write deadlock fixes. It should be fairly
> unlikely to cause you a deadlock. You could give this quick patch a
> try, though. Does it fix your problem?



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