On Tue, Oct 21, 2014 at 03:46:02AM +0000, Drokin, Oleg wrote: > Hello! > > On Oct 20, 2014, at 9:13 PM, Al Viro wrote: > > > a) what protects ->d_name in ll_intent_file_open()? It copies > > ->d_name.name and ->d_name.len into local variables and proceeds to > > use those; what's to guarantee that dentry won't get hit with d_move() > > halfway through that? None of the locks that would give an exclusion > > against d_move() appear to be held… > > You are right. We hit something very similar not too long ago. Umm... While we are at it - what's the story with ll_setxattr() handling of "trusted.lov"? What happens on the protocol level and why do we need a file name for that, while for directories we don't seem to need it? -- 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
