mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-11-02 11:21:12 +00:00
0a8a79af53
Detected by Coverity. Both are instances of bad things happening if pipe2 fails; the virNetClientNew failure could free garbage, and virNetSocketNewConnectCommand could close random fds. Note: POSIX doesn't guarantee the contents of fd[0] and fd[1] after pipe failure: http://austingroupbugs.net/view.php?id=467 We may need to introduce a virPipe2 wrapper that guarantees that on pipe failure, the fds are explicitly set to -1, rather than our current state of assuming the fds are unchanged from their value prior to the failed pipe call. * src/rpc/virnetclient.c (virNetClientNew): Initialize variable. * src/rpc/virnetsocket.c (virNetSocketNewConnectCommand): Likewise. |
||
---|---|---|
.. | ||
gendispatch.pl | ||
genprotocol.pl | ||
virnetclient.c | ||
virnetclient.h | ||
virnetclientprogram.c | ||
virnetclientprogram.h | ||
virnetclientstream.c | ||
virnetclientstream.h | ||
virnetmessage.c | ||
virnetmessage.h | ||
virnetprotocol.x | ||
virnetsaslcontext.c | ||
virnetsaslcontext.h | ||
virnetserver.c | ||
virnetserver.h | ||
virnetserverclient.c | ||
virnetserverclient.h | ||
virnetservermdns.c | ||
virnetservermdns.h | ||
virnetserverprogram.c | ||
virnetserverprogram.h | ||
virnetserverservice.c | ||
virnetserverservice.h | ||
virnetsocket.c | ||
virnetsocket.h | ||
virnettlscontext.c | ||
virnettlscontext.h |