e59d19628d
This is throwing errors in static analysis, complaining that comparing that a prior is higher and lower is impossible. That is wrong per my eyes (I swear I think it might be cueing off the names of the functions, which invert "higher" and "lower" to match our reversed priority numbers). But frankly this was never a very readable macro to begin with. Refactor to put the bounds into the term, so the static analyzer can prove it locally, and add a build assertion to catch any errors (there are none currently) where the low<->high priority range is invalid. Long term, we should probably remove this macro, it doesn't provide much value. But removing it in response to a static analysis failure is... not very responsible as a development practice. Fixes #14816 Fixes #14820 Signed-off-by: Andy Ross <andrew.j.ross@intel.com> |
||
|---|---|---|
| .. | ||
| gen_offset.h | ||
| kernel_internal.h | ||
| kernel_offsets.h | ||
| kernel_structs.h | ||
| ksched.h | ||
| kswap.h | ||
| offsets_short.h | ||
| syscall_handler.h | ||
| timeout_q.h | ||
| wait_q.h | ||