18 Feb
2017
18 Feb
'17
4:26 p.m.
On Wed, Jan 25, 2017 at 03:27:37PM -0500, John Ferlan wrote:
While perhaps improbable, it could be possible that after finding our object that another thread running essentially in parallel could attempt to delete the same vHBA.
So rather than dropping the lock right after finding the object, keep the lock around while we drop the object lock and work on deleting the object. Once the delete occurs we can safely drop the driver lock again.
Cleanup some of the usage of cleanup instead out for the goto label.
Signed-off-by: John Ferlan <jferlan@redhat.com> --- src/node_device/node_device_driver.c | 22 ++++++++++------------ 1 file changed, 10 insertions(+), 12 deletions(-)
ACK Pavel