On Mon, Dec 07, 2015 at 08:28:03AM -0500, Jeff Layton wrote: > My understanding is that you need to increment the seqid when prior to > sending the callback. The basic idea there is that you want to ensure > that any LAYOUTGETs that were sent before the CB_LAYOUTRECALL get back > an OLD_STATEID error. RFC5661, Section 12.5.3: > > After the layout stateid is established, the server increments by > one the value of the "seqid" in each subsequent LAYOUTGET and > LAYOUTRETURN response, and in each CB_LAYOUTRECALL request. True. Although I really don't see any way to make layoutrecall processing race free that way. I guess your patch to just drop the mutex is the best we could do. Note that it doesn't really matter for the current server, as we will always recall the whole file, and thus leave no layout state for it on the client. But for finger grained recalls this could become a problem. -- 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
