Previously:
* rc would not be set before leaving the function, with the
result that an uninitialised value would be returned
* failures of libxl__userdata_path would result in a NULL dereference
* failures of unlink() would not be usefully logged
This appears to be due to an attempt to avoid having to repeat the
call to libxl__unlock_domain_userdata by informally sharing parts of
the success and failure paths.
Change to use the canonical error-handling style:
* Initialise lock to 0.
* Do the unlock in the `out' section - always attempt to unlock
lock if it is non-0.
* Explicitly set rc and `goto out' on all error paths, even
those right at the end of the function.
* Add an error check for filename = libxl__userdata_path(...);
Coverity-ID:
1240237,
1240235.
CC: Wei Liu <wei.liu2@citrix.com>
CC: coverity@xenproject.org
Reviewed-by: Andrew Cooper<andrew.cooper3@citrix.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
const char *userdata_userid)
{
GC_INIT(ctx);
- int rc;
+ CTX_LOCK;
- libxl__domain_userdata_lock *lock;
+ int rc;
+ libxl__domain_userdata_lock *lock = NULL;
const char *filename;
- CTX_LOCK;
lock = libxl__lock_domain_userdata(gc, domid);
if (!lock) {
rc = ERROR_LOCK_FAIL;
}
filename = libxl__userdata_path(gc, domid, userdata_userid, "d");
- if (unlink(filename)) rc = ERROR_FAIL;
+ if (!filename) {
+ rc = ERROR_FAIL;
+ goto out;
+ }
+ if (unlink(filename)) {
+ LOGE(ERROR, "error deleting userdata file: %s", filename);
+ rc = ERROR_FAIL;
+ goto out;
+ }
- libxl__unlock_domain_userdata(lock);
+ rc = 0;
out:
+ if (lock)
+ libxl__unlock_domain_userdata(lock);
CTX_UNLOCK;
GC_FREE;
return rc;