Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[git\s+pull\]\s+dentry_unhash\(\)\s+breakage\s*$/: 4 ]

Total 4 documents matching your query.

1. [git pull] dentry_unhash() breakage (score: 1)
Author: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Date: Mon, 30 May 2011 06:56:01 +0100
A couple of dentry_unhash fallout fixes Please, pull from usual place - git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git/ for-linus Al Viro (1): autofs4: bogus dentry_unhash() added in
/archives/xfs/2011-05/msg00355.html (9,109 bytes)

2. Re: [git pull] dentry_unhash() breakage (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Mon, 30 May 2011 04:59:22 -0400
Shouldn't we do the shrink_dcache_parent only after a successfull rmdir or rename?
/archives/xfs/2011-05/msg00356.html (8,850 bytes)

3. Re: [git pull] dentry_unhash() breakage (score: 1)
Author: Sage Weil <sage@xxxxxxxxxxxx>
Date: Tue, 31 May 2011 09:26:52 -0700 (PDT)
Yeah, that makes more sense to me... sage Only prune the dentries of the rmdir or dir rename succeeds. Doing so on failure makes no sense (though it's mostly harmless). Signed-off-by: Sage Weil <sage
/archives/xfs/2011-05/msg00372.html (11,435 bytes)

4. Re: [git pull] dentry_unhash() breakage (score: 1)
Author: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Date: Tue, 31 May 2011 18:33:48 +0100
No, it doesn't. Let's keep changes to minimum. I *really* don't want to audit autofs and hell knows how many other places for more or less subtle breakage caused by that. It's bad enough as it is...
/archives/xfs/2011-05/msg00373.html (10,120 bytes)


This search system is powered by Namazu