linux-kernel - Re: lockdep: inconsistent lock state

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: <alpine.DEB.2.01.0912271355550.3483@bogon.housecafe.de>
Date:	Sun, 27 Dec 2009 14:01:07 -0800 (PST)
From:	Christian Kujau <lists@...dbynature.de>
To:	Dave Chinner <david@...morbit.com>
cc:	xfs@....sgi.com, LKML <linux-kernel@...r.kernel.org>
Subject: Re: lockdep: inconsistent lock state

On Mon, 28 Dec 2009 at 08:27, Dave Chinner wrote:
> 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....

OK, thanks for confirming this. I've only seen this during
bonnie++ tests so far, and it's always reproducible there, but
I've not seen it during "normal use". It's still scary though. Just 
checked, opensuse and fedora have CONFIG_LOCKDEP_SUPPORT=y but no 
related DEBUG options set, so it probably won't ever show up for
the general public.

Christian.
-- 
BOFH excuse #278:

The Dilithium Crystals need to be rotated.
--
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/