On Thu, Jan 23, 2014 at 04:27:00PM -0500, J. Bruce Fields wrote: > From: "J. Bruce Fields" <bfields@xxxxxxxxxx> > > d_splice_alias can create duplicate directory aliases (in the !new > case), or (in the new case) d_move directories without holding > appropriate locks. Details, please. In the new case, we have IS_ROOT() alias found; what locks would that need? Note that d_materialise_unique() won't bother with __d_unalias() in such case - it does what d_move() would've done, without taking any mutex. In the !new case, we'd need a preexisting dentry alias, complete with parent. IOW, that's the case when directory already in the tree has been found during lookup from another parent. In which case we shouldn't be using d_splice_alias() at all, as it is (and it certainly can't happen for any local fs). Now, I agree that merging that with d_materialise_unique() might be a good idea, but commit message is wrong as it, AFAICS. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
