> Should that be fixed in the Linux kernel, or at least reported to the
developers?
tl;dr: I don't have insight to the relevant community, but it may be
worth reporting to either the kernel community or the apparmor devs.
Context: I'm just a random user who did the analysis, not an Ubuntu or
Debi
This message doesn't seem to affect anything, from what I can tell.
Here's a technical analysis.
The system call, sched_setattr, is being made in glib's
g_system_thread_get_scheduler_settings. It gets the current scheduling
settings, and then tests to make sure it can set them on the same
thread.
2 matches
Mail list logo
