[libfabric-users] CQ permission denied (-EACCES)

[Hefty, Sean]

> One issue I still see in our runtime unit tests is a condition where the
> remote CQ data (immediate) indicates that a write has completed at the
> target, but when I go to check the associated region the read value is
> not as expected.  I assumed that the semantics of popping immediate data
> guaranteed that the writing of the destination buffer has been
> successfully completed.  Is this an incorrect assumption for libfabric

This is a correct assumption.  The CQ entry should not be generated until the operation has completed and the data is readable.