> > Unfortunately this patch doesn't completely solve this problem, since > > the system will still be hosed due to all memory being used up by > > dentries. And I bet the OOM killer won't find the real target (du) > > but will kill anything before that. > > > > So the second part of the problem is to somehow limit the number of > > dentries used. Not easy... > > At least with this patch (if I am reading it correctly), once the offending > culprit is identified and the programs are killed off, everything will go > back to normal without a reboot. Yes, it's basically a "normal" OOM situation. What makes it worse than usual, is that it's _kernel_ memory being used up which is not attributed to any process. So from the OOM killer's point of view it looks like none of the userspace programs are responsible for the OOM, and it will just select targets randomly. By the time it has come to the actual culprits (the filesystem daemon and 'du') it will have killed almost everything useful. So it's definitely better than without the patch, but still has room for improvement. Thanks, Miklos - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
