This behavior is currently not possible with the default preemption model used in most distributions, PREEMPT_VOLUNTARY. For many products using BPF for tracing/security, this would constitute a regression in terms of reliability. My question is whether there is any ongoing work to fix this behavior of kprobes and tracepoints, so they do not miss on nesting. I have previously been told that there is ongoing work related to bpf-specific spinlocks to resolve this problem [2]. Will that be available by the time this is merged into the mainline, and the current defaults deprecated? Thanks, Usama Saqib. 1. https://lwn.net/ml/all/20241007074609.447006177@xxxxxxxxxxxxx/ 2. https://lore.kernel.org/bpf/CAOzX8ixsxPbw1ke=DsDd_b38k1TE+JRG3LvJfh4wD60mhHvAqA@xxxxxxxxxxxxxx/T/#m206e33e5a0a0d9d3d498480a53aa9c87c81d91ff
