On Fri, 2009-03-20 at 00:34 +0900, hooanon05@xxxxxxxxxxx wrote: > If you remember why you discarded the FS_NO_LOOKUP_IN_READDIR flag > approach, please let me know. URL or something is enough. I was just lamenting that decision. I think someone persuaded me that the extra complexity wasn't worth it, and that we should just do it unconditionally. One option would be to restore the FS_NO_LOOKUP_IN_READDIR flag, and document that it means that your ->lookup is called _without_ i_mutex held. That would actually be OK in all cases that need the flag, I believe (since the whole point in those cases is that they have their _own_ locking which is why we did it in the first place). -- David Woodhouse Open Source Technology Centre David.Woodhouse@xxxxxxxxx Intel Corporation -- 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
