As discussed in Message-ID <20200714165621.ga3...@nazgul.tnic>. We all agree that userspace MSR twiddling is non-ideal, but we should be a bit cautious of taking up too much kmsg buffer if applications do repeated writes. `allow_writes=1` is possible, but is non-ideal (see patch 1 changelog).
Also added pid information to the message, since it makes identification of the source (more or less) unambiguous. Chris Down (2): x86: Prevent userspace MSR access from dominating the console x86: Make source of unrecognised MSR writes unambiguous arch/x86/kernel/msr.c | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) -- 2.28.0
