lkml.org 
[lkml]   [2009]   [Dec]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: lockdep: inconsistent lock state
On Sat, Dec 26, 2009 at 01:07:49PM -0800, Christian Kujau wrote:
> Hi,
>
> during tests with bonnie++ on an XFS filesystem, the warning below is
> issued. From the message's timestamps, the warning occurs during the
> "Create files in sequential order" phase. I've put a few more details and
> the config here: http://nerdbynature.de/bits/2.6.33-rc2/xfs_ilock
>
> Something similar has been reported in http://lkml.org/lkml/2009/2/20/269
> (for 2.6.29-rc5) and a fix for this false positive made its way into
> mainline as ed93ec3907f063268ced18728d0653f6199d100c - so I take it this
> is a different issue then?

This is the usual false positive that is detected - XFS takes locks in
reclaim that it also takes in non-reclaim paths. The reclaim path
from kswapd inverts lock ordering and so we get this report. This
case has never been a deadlock case because an inode in reclaim
cannot be referenced by any other path, so once again it is a
false positive....
Cheers,

Dave.
--
Dave Chinner
david@fromorbit.com


\
 
 \ /
  Last update: 2009-12-27 22:29    [from the cache]
©2003-2011 Jasper Spaans