On Thu, 4 Feb 2021 21:48:35 +0100 Pavel Machek <[email protected]> wrote: > > + pr_warn("** Kernel memory addresses are exposed, which may **\n"); > > + pr_warn("** compromise security on your system. > > **\n"); > > This is lies, right? And way too verbose.
Not really. More of an exaggeration than a lie. And the verbosity is to make sure it's noticed by those that shouldn't have it set. This works well for keeping trace_printk() out of production kernels. Why do you care anyway, you are just debugging it, and it shouldn't trigger any bug reports on testing infrastructure. That's why I like the notice. It gets the job done of keeping people from using things they shouldn't be using, and doesn't cause testing failures that a WARN_ON would. -- Steve
