| 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
| ||
|
Date: Tue, 8 Mar 2011 16:21:45 +0100 From: Bastien ROUCARIES <roucaries.bastien@...il.com> To: Frederic Weisbecker <fweisbec@...il.com> Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>, akpm@...ux-foundation.org Subject: Re: Reiserfs deadlock in 2.6.36 >> >> Doing a while true;do sync && sleep1; done; help a lot > > Which kernel are you running by the way? 2.6.37 now > >> > >> > I don't know what to do yet. I need to think more about it. >> > >> >> Could we do the stuff I have sugested at first ? use lockdep to track >> journal open,/close using fake lock ? > > I don't think it's not an adapted test. Lockdep is useful to detect lock inversion > scenarios but that's not very useful to detect a lock that takes too much time > to be released. For that we have the hung task detector, whose report we already > have. > >> BTW it seems that someone experiment this confition on ext3. I could >> do more testing if you want, and I will run xfstests in order to see >> if I could reproduce more quickly > > I'm not sure the file corruption and the deadlock are linked. But > may be xfstest can provoke the deadlock (or the file corruption) > more quickly. It's pretty good at stressing file systems. > Do you know a test number to try ? Bastien -- 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