| 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
| ||
|
Message-Id: <1190671658.6700.31.camel@heimdal.trondhjem.org>
Date: Mon, 24 Sep 2007 18:07:38 -0400
From: Trond Myklebust <Trond.Myklebust@...app.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>
Cc: linux-kernel@...r.kernel.org
Subject: lockdep wierdness...
I'm seeing lockdep warning about a potential lock inversion between
&mm->mmap_sem and &inode->i_mutex in NFS (see attachment).
Unfortunately the basis for the warning appears to be the behaviour in
ext3(???). AFAICS there is no way for NFS to share an inode->i_mutex
with ext3. What to do?
Trond
View attachment "wierd_lockdep.txt" of type "text/plain" (2363 bytes)
Powered by blists - more mailing lists