lwp: Fix possible memory leak from scan-build 80/13080/3
authorPat Riehecky <riehecky@fnal.gov>
Wed, 23 May 2018 20:42:09 +0000 (15:42 -0500)
committerBenjamin Kaduk <kaduk@mit.edu>
Fri, 25 May 2018 01:52:59 +0000 (21:52 -0400)
commit55013a111394052a0253c87a744d03dfabd1be75
treecbe6503123a194052fe3923b93fb2e127f074c6b
parent850c7c50dccbdebb8e0a44da4fc7840760d9e02d
lwp: Fix possible memory leak from scan-build

It is possible for LWP_CreateProcess to return early. When it does, it
should free up any memory it allocated before leaving scope.

Change-Id: Ib5644d36dc01bbac33804f4a039661ce2c78969d
Reviewed-on: https://gerrit.openafs.org/13080
Reviewed-by: Andrew Deason <adeason@sinenomine.net>
Reviewed-by: Marcio Brito Barbosa <mbarbosa@sinenomine.net>
Reviewed-by: Mark Vitale <mvitale@sinenomine.net>
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Benjamin Kaduk <kaduk@mit.edu>
src/lwp/lwp.c