Searched hist:"88 be7b4be4aa17c88247e162bdd7577ea79db94f" (Results 1 – 6 of 6) sorted by relevance
/openbmc/qemu/block/ |
H A D | snapshot.c | diff 88be7b4be4aa17c88247e162bdd7577ea79db94f Fri May 20 11:49:07 CDT 2016 Kevin Wolf <kwolf@redhat.com> block: Fix bdrv_next() memory leak
The bdrv_next() users all leaked the BdrvNextIterator after completing the iteration. Simply changing bdrv_next() to free the iterator before returning NULL at the end of list doesn't work because some callers exit the loop before looking at all BDSes.
This patch moves the BdrvNextIterator from the heap to the stack of the caller and switches to a bdrv_first()/bdrv_next() interface for initialising the iterator.
Signed-off-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Fam Zheng <famz@redhat.com>
|
H A D | block-backend.c | diff 88be7b4be4aa17c88247e162bdd7577ea79db94f Fri May 20 11:49:07 CDT 2016 Kevin Wolf <kwolf@redhat.com> block: Fix bdrv_next() memory leak
The bdrv_next() users all leaked the BdrvNextIterator after completing the iteration. Simply changing bdrv_next() to free the iterator before returning NULL at the end of list doesn't work because some callers exit the loop before looking at all BDSes.
This patch moves the BdrvNextIterator from the heap to the stack of the caller and switches to a bdrv_first()/bdrv_next() interface for initialising the iterator.
Signed-off-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Fam Zheng <famz@redhat.com>
|
H A D | io.c | diff 88be7b4be4aa17c88247e162bdd7577ea79db94f Fri May 20 11:49:07 CDT 2016 Kevin Wolf <kwolf@redhat.com> block: Fix bdrv_next() memory leak
The bdrv_next() users all leaked the BdrvNextIterator after completing the iteration. Simply changing bdrv_next() to free the iterator before returning NULL at the end of list doesn't work because some callers exit the loop before looking at all BDSes.
This patch moves the BdrvNextIterator from the heap to the stack of the caller and switches to a bdrv_first()/bdrv_next() interface for initialising the iterator.
Signed-off-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Fam Zheng <famz@redhat.com>
|
/openbmc/qemu/include/block/ |
H A D | block.h | diff 88be7b4be4aa17c88247e162bdd7577ea79db94f Fri May 20 11:49:07 CDT 2016 Kevin Wolf <kwolf@redhat.com> block: Fix bdrv_next() memory leak
The bdrv_next() users all leaked the BdrvNextIterator after completing the iteration. Simply changing bdrv_next() to free the iterator before returning NULL at the end of list doesn't work because some callers exit the loop before looking at all BDSes.
This patch moves the BdrvNextIterator from the heap to the stack of the caller and switches to a bdrv_first()/bdrv_next() interface for initialising the iterator.
Signed-off-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Fam Zheng <famz@redhat.com>
|
/openbmc/qemu/ |
H A D | blockdev.c | diff 88be7b4be4aa17c88247e162bdd7577ea79db94f Fri May 20 11:49:07 CDT 2016 Kevin Wolf <kwolf@redhat.com> block: Fix bdrv_next() memory leak
The bdrv_next() users all leaked the BdrvNextIterator after completing the iteration. Simply changing bdrv_next() to free the iterator before returning NULL at the end of list doesn't work because some callers exit the loop before looking at all BDSes.
This patch moves the BdrvNextIterator from the heap to the stack of the caller and switches to a bdrv_first()/bdrv_next() interface for initialising the iterator.
Signed-off-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Fam Zheng <famz@redhat.com>
|
H A D | block.c | diff 88be7b4be4aa17c88247e162bdd7577ea79db94f Fri May 20 11:49:07 CDT 2016 Kevin Wolf <kwolf@redhat.com> block: Fix bdrv_next() memory leak
The bdrv_next() users all leaked the BdrvNextIterator after completing the iteration. Simply changing bdrv_next() to free the iterator before returning NULL at the end of list doesn't work because some callers exit the loop before looking at all BDSes.
This patch moves the BdrvNextIterator from the heap to the stack of the caller and switches to a bdrv_first()/bdrv_next() interface for initialising the iterator.
Signed-off-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Fam Zheng <famz@redhat.com>
|