| commit | d656ec5ea823bcdb59b6512cb73b3f2f97a8308f | |
| author | Daniel P. Berrange <berrange@redhat.com> | |
| Wed, 27 Apr 2016 10:04:52 +0000 (27 11:04 +0100) | ||
| committer | Amit Shah <amit.shah@redhat.com> | |
| Thu, 26 May 2016 06:01:09 +0000 (26 11:31 +0530) | ||
| tree | b48ee797db2d516b2b84622f8e5c000ae46775b0 | treesnapshot (tar.gz zip) |
| parent | 1fd791f007821e2510899e60be0ddad3077120e3 | commitdiff |
io: avoid double-free when closing QIOChannelBuffer
The QIOChannelBuffer's close implementation will free
the internal data buffer. It failed to reset the pointer
to NULL though, so when the object is later finalized
it will free it a second time with predictable crash.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Message-Id: <1461751518-12128-3-git-send-email-berrange@redhat.com>
Signed-off-by: Amit Shah <amit.shah@redhat.com>
The QIOChannelBuffer's close implementation will free
the internal data buffer. It failed to reset the pointer
to NULL though, so when the object is later finalized
it will free it a second time with predictable crash.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Message-Id: <1461751518-12128-3-git-send-email-berrange@redhat.com>
Signed-off-by: Amit Shah <amit.shah@redhat.com>
| io/channel-buffer.c | diffblobblamehistory |