On Tue, Sep 18, 2012 at 04:58:24PM -0400, Banerjee, Debabrata wrote: > On 9/18/12 4:04 PM, "J. Bruce Fields" <bfields@xxxxxxxxxxxx> wrote: > > >On Mon, Sep 17, 2012 at 06:53:16PM -0400, Banerjee, Debabrata wrote: > >[229978.873082] Pid: 11817, comm: xxxxxxxx. Not tainted 3.0.30-3.0.1-amd64 > > > >What's 3.0.30-3.0.1? Is this reproduceable with an upstream kernel? > > > >--b. > > An internal build number, it's 3.0.30. But it looks like line 2105 of 3.0.30 is a comment?: $ git show v3.0.30:fs/dcache.c |nl|grep '2105' 2105 * This helper attempts to cope with remotely renamed directories $ git grep -n 'BUG_ON(!d_unhashed(entry))' v3.0.30:fs/dcache.c v3.0.30:fs/dcache.c:2077: BUG_ON(!d_unhashed(entry)); Just curious. --b. > Also I already skimmed for relevant > patches to fs/ext2/* and fs/dcache* in stable and mainline and could find > none. My best guess right now is a race somewhere in ext2, dentry must get > rehashed between __d_drop(dentry) and __d_rehash(dentry,Š) in __d_move(). > > -Debabrata > -- 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
