5ec008a2bd
The functions qemu_get_timedate() and qemu_timedate_diff() take and return a time offset as an integer. Coverity points out that means that when an RTC device implementation holds an offset as a time_t, as the m48t59 does, the time_t will get truncated. (CID 1507157, 1517772). The functions work with time_t internally, so make them use that type in their APIs. Note that this won't help any Y2038 issues where either the device model itself is keeping the offset in a 32-bit integer, or where the hardware under emulation has Y2038 or other rollover problems. If we missed any cases of the former then hopefully Coverity will warn us about them since after this patch we'd be truncating a time_t in assignments from qemu_timedate_diff().) Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org> |
||
---|---|---|
.. | ||
accel-blocker.h | ||
accel-ops.h | ||
arch_init.h | ||
balloon.h | ||
block-backend-common.h | ||
block-backend-global-state.h | ||
block-backend-io.h | ||
block-backend.h | ||
block-ram-registrar.h | ||
blockdev.h | ||
cpu-throttle.h | ||
cpu-timers.h | ||
cpus.h | ||
cryptodev-vhost-user.h | ||
cryptodev-vhost.h | ||
cryptodev.h | ||
device_tree.h | ||
dirtylimit.h | ||
dirtyrate.h | ||
dma.h | ||
dump-arch.h | ||
dump.h | ||
event-loop-base.h | ||
hax.h | ||
hostmem.h | ||
hvf_int.h | ||
hvf.h | ||
hw_accel.h | ||
iothread.h | ||
kvm_int.h | ||
kvm_xen.h | ||
kvm.h | ||
memory_mapping.h | ||
numa.h | ||
nvmm.h | ||
os-posix.h | ||
os-win32.h | ||
qtest.h | ||
replay.h | ||
reset.h | ||
rng-random.h | ||
rng.h | ||
rtc.h | ||
runstate-action.h | ||
runstate.h | ||
seccomp.h | ||
stats.h | ||
sysemu.h | ||
tcg.h | ||
tpm_backend.h | ||
tpm_util.h | ||
tpm.h | ||
vhost-user-backend.h | ||
watchdog.h | ||
whpx.h | ||
xen-mapcache.h | ||
xen.h |