Re: [PATCH] Busy inodes after unmount, be more verbose in generic_shutdown_super

[Kirill Korotaev]

> > CPU 1				CPU 2
> > ~~~~~				~~~~~
> > umount /dev/sda1
> > generic_shutdown_super          shrink_dcache_memory()
> > shrink_dcache_parent            dput dentry
> > select_parent                   prune_one_dentry()
> >                                <<<< child is dead, locks are released,
> >                                  but parent is still referenced!!! >>>>
> > skip dentry->parent,
> > since it's d_count > 0
> >
> > message: BUSY inodes after umount...
> >                                <<< parent is left on dentry_unused list,
> >                                   referencing freed super block >>>
>
>
> I see. The problem is that dcache_lock is given up before dereferencing the
> parent. But your patch seems to be wrong anyway IMHO. I'll post patches in a
> seperate thread.
Jan, I still have not heard a single comment about what's wrong with 
it... I would really appreciate if you provide me one.

Kirill

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/