c0183fdedd
There was a detected user error in the code where racing insertions of k_delayed_work items into different queues would be detected and flagged as an error (honestly I don't see much value there -- Zephyr doesn't as a general rule protect against errors like this, and work_q's are inherently kernel things that don't require userspace-style checking). This got broken with spinlockification, where each work_q object got its own lock, so the single lock wouldn't protect against the other insert function any more. As it happens, that was needless. The core synchronization on a work_q is in the internal k_queue object anyway -- the lock in this file was only ever used for (very fast, noncontending) delayed work insertion. So go back to a global lock to preserve the original behavior. Fixes #14104 Signed-off-by: Andy Ross <andrew.j.ross@intel.com> |
||
---|---|---|
.. | ||
include | ||
atomic_c.c | ||
CMakeLists.txt | ||
compiler_stack_protect.c | ||
device.c | ||
errno.c | ||
idle.c | ||
init.c | ||
int_latency_bench.c | ||
Kconfig | ||
Kconfig.power_mgmt | ||
mailbox.c | ||
mem_domain.c | ||
mem_slab.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.c | ||
thread_abort.c | ||
timeout.c | ||
timer.c | ||
userspace.c | ||
userspace_handler.c | ||
version.c | ||
work_q.c |