On Sun, May 4, 2014 at 8:29 AM, Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote: > On Sat, May 03, 2014 at 07:21:11PM +0100, Al Viro wrote: >> On Sat, May 03, 2014 at 05:26:04AM +0100, Al Viro wrote: >> >> > See vfs.git#dentry_kill-3; warning - this is completely untested and I would >> > really like comments on spinning case there (i.e. the one where select_collect() >> > finds some stuff already on some other shrink list and nothing with zero >> > refcount that wouldn't be there). In that case (and it's basically "somebody >> > else is evicting stuff in our subtree and they'd already picked everything >> > we want evicted") I just let the loop in check_submounts_and_drop() repeat >> > (we do have cond_resched() there). Any better suggestions would be welcome... >> >> Hmm... As the matter of fact, the whole shrink_dcache_for_umount() could >> be made a lot saner. What we need is to reuse shrink_dcache_parent() >> and follow it with d_walk() that would just go through whatever remains and >> complain about the leaves of that. For anon roots we'll obviously need to >> wrap that into dget and d_drop/dput. >> >> I'm testing that right now; everything seems to be working so far and if >> it survives, I'll push that sucker out. Total since the beginning of >> the whole series: >> fs/dcache.c | 310 ++++++++++++++++++++++++++++++++--------------------------------------------------------- >> include/linux/dcache.h | 2 + >> 2 files changed, 112 insertions(+), 200 deletions(-) > > No regressions compared to mainline; force-pushed into vfs#dentry_kill-3. > Review and testing would be very welcome... Summary for that branch: > (it's *not* a pull request yet; the thing really needs review) Patches look okay to me. Reviewed-by: Miklos Szeredi <mszeredi@xxxxxxx> > dentry_kill(): don't try to remove from shrink list Backport of this to 3.12 was tested by IBM and apparently fixes the issue for them (I didn't backport the cleanup patches only the actual fix) > don't remove from shrink list in select_collect() I've also asked them to test this, although I think this is even harder to trigger. But at least the non-racy codepaths need to be tested. 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
