I think the series introduces some find vs alloc races where a function first tries to find an existing structure in a lookup structure, then allocates a new one, but doesn't check for another allocation that could have happened in the meantime. - lookup_or_create_lock_state for lock stateids - I can't find any protection for the creation/addition of files and open stateids in the whole open machinery (nfsd4_open, nfsd4_process_open1 and nfsd4_process_open2), but I also generally have trouble following that code. - similarly I can't find much of a protection against this sort of race for the various state owners. -- 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
