| commit | c8a9fd80719e63615dac12e3625223fb54aa8430 | |
| author | Fam Zheng <famz@redhat.com> | |
| Wed, 1 Jun 2016 01:52:23 +0000 (1 09:52 +0800) | ||
| committer | Stefan Hajnoczi <stefanha@redhat.com> | |
| Tue, 7 Jun 2016 13:40:51 +0000 (7 14:40 +0100) | ||
| tree | 98ed133c8e23c47d3992a56ab934e1a870fc7ab5 | treesnapshot (tar.gz zip) |
| parent | 41574268b7e61ab98384ca7048f3fec862433401 | commitdiff |
block: Drop bdrv_ioctl_bh_cb
Similar to the "!drv || !drv->bdrv_aio_ioctl" case above, here it is
okay to set co.ret and return. As pointed out by Paolo, a BH will be
created as necessary by the caller (bdrv_co_maybe_schedule_bh).
Besides, as pointed out by Kevin, "data" was leaked before.
Reported-by: Kevin Wolf <kwolf@redhat.com>
Reported-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Fam Zheng <famz@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Message-id: 20160601015223.19277-1-famz@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Similar to the "!drv || !drv->bdrv_aio_ioctl" case above, here it is
okay to set co.ret and return. As pointed out by Paolo, a BH will be
created as necessary by the caller (bdrv_co_maybe_schedule_bh).
Besides, as pointed out by Kevin, "data" was leaked before.
Reported-by: Kevin Wolf <kwolf@redhat.com>
Reported-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Fam Zheng <famz@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Message-id: 20160601015223.19277-1-famz@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
| block/io.c | diffblobblamehistory |