On 11/17/20 8:26 AM, Robert Marcano wrote:
User d9k on IRC found the culprit. It is low-memory-monitor. The latest
commit [1] for it tries to not mess with the value with 1 is set, but it
should not mess with it ever.
The same documentation on that commit references [2] where it says:
Note that the value of ``/proc/sys/kernel/sysrq`` influences only the
invocation
via a keyboard. Invocation of any operation via
``/proc/sysrq-trigger`` is
always allowed (by a user with admin privileges).
[1]
https://gitlab.freedesktop.org/hadess/low-memory-monitor/-/commit/11560bc102941c95890c0852f2d9b166853b4f6a
[2]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/admin-guide/sysrq.rst
Will submit a bug (if d9k already hasn't done that).
Reported upstream and a tracking bug on bugzilla
https://gitlab.freedesktop.org/hadess/low-memory-monitor/-/issues/11
https://bugzilla.redhat.com/show_bug.cgi?id=1898524
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
