| 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: <20140330235717.GO18016@ZenIV.linux.org.uk> Date: Mon, 31 Mar 2014 00:57:17 +0100 From: Al Viro <viro@...IV.linux.org.uk> To: Dave Chinner <david@...morbit.com> Cc: Dave Jones <davej@...hat.com>, Linux Kernel <linux-kernel@...r.kernel.org>, xfs@....sgi.com Subject: Re: xfs i_lock vs mmap_sem lockdep trace. On Mon, Mar 31, 2014 at 10:43:35AM +1100, Dave Chinner wrote: > filldir on a directory inode vs page fault on regular file. Known > issue, definitely a false positive. We have to change locking > algorithms to avoid such deficiencies of lockdep (a case of "lockdep > considered harmful", perhaps?) so it's not something I'm about to > rush... Give i_lock on directories a separate class, as it's been done for i_mutex... -- 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/
Powered by blists - more mailing lists