I don't see how we can have a delegation conflict here. If a client
has a write delegation then there should not be any delegations from
other clients.
A delegation conflict is possible if the client is using an
anonymous stateid to perform the READ.
One thing we could perhaps do is add support for the use of
anonymous stateids as a separate patch. Sagi, how necessary is
support for "READ with anonymous stateid" for supporting WR_ONLY
write delegation?
Without this in the patch, there is a pynfs tests that breaks (read with
anon stateid).
I can separate it if you want, but didn't want to introduce a patch that
causes a regression
on its own.
