mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-02 11:12:59 +00:00
12bd187003
The "forever" token has always been interpreted above z_add_timeout() (because it's always taken ticks, but K_FOREVER used to be in ms). But it was discovered that k_delayed_work_submit_to_queue() was never testing for this and passing a raw K_FOREVER down, where it got interpreted as a negative timeout and caused it to fire at the next tick. Now that we actually see the original k_timeout_t here, we might as well check it locally and do the correct thing (that is, nothing) if asked to schedule a timeout that will never fire. Fixes #24409 Signed-off-by: Andy Ross <andrew.j.ross@intel.com> |
||
|---|---|---|
| .. | ||
| include | ||
| atomic_c.c | ||
| CMakeLists.txt | ||
| compiler_stack_protect.c | ||
| device.c | ||
| errno.c | ||
| fatal.c | ||
| futex.c | ||
| idle.c | ||
| init.c | ||
| Kconfig | ||
| Kconfig.power_mgmt | ||
| kheap.c | ||
| mailbox.c | ||
| mem_domain.c | ||
| mem_slab.c | ||
| mempool_sys.c | ||
| mempool.c | ||
| msg_q.c | ||
| mutex.c | ||
| pipes.c | ||
| poll.c | ||
| queue.c | ||
| sched.c | ||
| sem.c | ||
| smp.c | ||
| stack.c | ||
| system_work_q.c | ||
| thread_abort.c | ||
| thread.c | ||
| timeout.c | ||
| timer.c | ||
| userspace_handler.c | ||
| userspace.c | ||
| version.c | ||
| work_q.c | ||