> Furthermore, the private copy isn't correct already in case > sysrq_always_enabled is true. So, remove __sysrq_enabled and use a > getter-helper for sysrq enabled status. Since the old way was known to be unreliable, the new way looks like a great candidate for a KUnit test. Off topic: I wonder if Magic Sysrq could be extended with reasonable effort to be triggered by a sequence of keystrokes which would be less likely to be generated by a noisy serial.
