Revision eefd95e1f3d47b90dc768e9ebc77d390c4f34809 authored by Shuah Khan on 21 September 2017, 19:05:18 UTC, committed by Shuah Khan on 25 September 2017, 16:09:07 UTC
When timer_create() fails on a bootime or realtime clock, setup_timer() returns 0 as if timer has been set. Callers wait forever for the timer to expire. This hang is seen on a system that doesn't have support for: CLOCK_REALTIME_ALARM ABSTIME missing CAP_WAKE_ALARM? : [UNSUPPORTED] Test hangs waiting for a timer that hasn't been set to expire. Fix setup_timer() to return 1, add handling in callers to detect the unsupported case and return 0 without waiting to not fail the test. Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
1 parent 01db7fb
File | Mode | Size |
---|---|---|
.gitignore | -rw-r--r-- | 151 bytes |
Kconfig | -rw-r--r-- | 7.8 KB |
Makefile | -rw-r--r-- | 2.0 KB |
gen_init_cpio.c | -rw-r--r-- | 12.7 KB |
initramfs_data.S | -rw-r--r-- | 1.3 KB |
Computing file changes ...