vSockets on Linux tries to claim an address family starting from the top
of the valid range. If someone has already claimed an address, we will
print a warning to the kernel log and then continue looping. This
warning started appearing on Cent OS 5.4 in autoinstall tests, presumably
because someone is grabbing the top family. Because the automation is
screenshot-based, the presence of the warning is causing the test to fail.
Fixed by moving the warning to the very end.
Signed-off-by: Dmitry Torokhov <dtor@vmware.com>
vsockVmciFamilyOps.family = i;
err = sock_register(&vsockVmciFamilyOps);
if (err) {
- Warning("Could not register address family %d.\n", i);
vsockVmciFamilyOps.family = VSOCK_INVALID_FAMILY;
} else {
vsockVmciDgramOps.family = i;
}
}
+ if (VSOCK_INVALID_FAMILY == vsockVmciFamilyOps.family) {
+ Warning("Could not register address family.\n");
+ }
+
return err;
}
#ifndef _VSOCK_VERSION_H_
#define _VSOCK_VERSION_H_
-#define VSOCK_DRIVER_VERSION 9.5.3.0
-#define VSOCK_DRIVER_VERSION_COMMAS 9,5.3,0
-#define VSOCK_DRIVER_VERSION_STRING "9.5.3.0"
+#define VSOCK_DRIVER_VERSION 9.5.4.0
+#define VSOCK_DRIVER_VERSION_COMMAS 9,5.4,0
+#define VSOCK_DRIVER_VERSION_STRING "9.5.4.0"
#endif /* _VSOCK_VERSION_H_ */