| 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: <20070530002857.GW85884050@sgi.com> Date: Wed, 30 May 2007 10:28:57 +1000 From: David Chinner <dgc@....com> To: Jeff Layton <jlayton@...hat.com> Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] add procfs tunable to enable immediate panic when there are busy inodes after umount On Tue, May 29, 2007 at 11:40:42AM -0400, Jeff Layton wrote: > After spending quite a bit of time tracking down a "VFS: busy inodes > after unmount" problem, it occurs to me that it would be nice to be > able to force a panic when that occurs. While an oops message alone is > not generally helpful for tracking down this sort of problem, > collecting and analyzing a coredump when this occurs can be. Agreed - we've found that we've had roughly 50% success in finding the cause of these problems from crash dumps triggered immediately like this vs ~0% from a crash that occurred some time later. Given that this problem will always result in a crash of the kernel at some random time in the future, why don't we just make this error an unconditional panic on get the crash over and done with? Cheers, Dave. -- Dave Chinner Principal Engineer SGI Australian Software Group - 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