On 7/7/22 3:27 PM, Mike Christie wrote: > When an app does a pr_reserve it will go to whatever path we happen to > be using at the time. This can result in errors where the app does a > second pr_reserve call and expects success but gets a failure becuase > the reserve is not done on the holder's path. This patch has us always > start trying to do reserves from the first path in the first group. >
Hi, Giving myself a review comment. pr_preempt can also establish a reservation. I meant to send a patch for that as well. If the approach in this patchset is ok, I'll send a patch for that as well. -- dm-devel mailing list [email protected] https://listman.redhat.com/mailman/listinfo/dm-devel
