From: Dmitry Safonov <dima@arista.com>
To: Jann Horn <jannh@google.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
Dmitry Safonov <0x7f454c46@gmail.com>,
Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Thomas Gleixner <tglx@linutronix.de>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [PATCH 2/3] x86/dumpstack: Add log_lvl to __show_regs()
Date: Thu, 25 Jun 2020 17:42:31 +0100 [thread overview]
Message-ID: <a0e7b79b-2ce7-f349-b308-e5329defd3fe@arista.com> (raw)
In-Reply-To: <CAG48ez3v9dHq1+jvPmvQapFRji=4XhA8iNurTGZeC6xoy7Qc1w@mail.gmail.com>
On 6/23/20 5:45 PM, Jann Horn wrote:
> On Tue, Jun 23, 2020 at 6:30 PM Dmitry Safonov <dima@arista.com> wrote:
>> show_trace_log_lvl() provides x86 platform-specific way to unwind
>> backtrace with a given log level. Unfortunately, registers dump(s) are
>> not printed with the same log level - instead, KERN_DEFAULT is always
>> used.
>>
>> Arista's switches uses quite common setup with rsyslog, where only
>> urgent messages goes to console (console_log_level=KERN_ERR), everything
>> else goes into /var/log/ as the console baud-rate often is indecently
>> slow (9600 bps).
>>
>> Backtrace dumps without registers printed have proven to be as useful as
>> morning standups. Furthermore, in order to introduce KERN_UNSUPPRESSED
>> (which I believe is still the most elegant way to fix raciness of sysrq[1])
>> the log level should be passed down the stack to register dumping
>> functions. Besides, I have a potential use-case for printing traces
>> with KERN_DEBUG level [2] (where registers dump shouldn't appear with
>> higher log level).
>>
>> Add log_lvl parameter to __show_regs().
>> Keep the used log level intact to separate visible change.
>
> This change seems like a good idea to me; just one small nit:
>
> [...]
>> void show_regs(struct pt_regs *regs)
>> {
>> + int print_kernel_regs;
>> +
>> show_regs_print_info(KERN_DEFAULT);
>>
>> - __show_regs(regs, user_mode(regs) ? SHOW_REGS_USER : SHOW_REGS_ALL);
>> + print_kernel_regs = user_mode(regs) ? SHOW_REGS_USER : SHOW_REGS_ALL;
>> + __show_regs(regs, print_kernel_regs, KERN_DEFAULT);
>
> print_kernel_regs should probably have type "enum show_regs_mode"?
Makes sense, will fix in v2.
Thanks,
Dmitry
next prev parent reply other threads:[~2020-06-25 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 16:29 [PATCH 0/3] x86/dumpstack: Print registers with the same log level as the backtrace Dmitry Safonov
2020-06-23 16:29 ` [PATCH 1/3] x86/dumpstack: Add log_lvl to show_iret_regs() Dmitry Safonov
2020-06-23 16:29 ` [PATCH 2/3] x86/dumpstack: Add log_lvl to __show_regs() Dmitry Safonov
2020-06-23 16:45 ` Jann Horn
2020-06-25 16:42 ` Dmitry Safonov [this message]
2020-06-23 16:29 ` [PATCH 3/3] x86/dumpstack: Show registers dump with trace's log level Dmitry Safonov
2020-06-24 6:50 ` [PATCH 0/3] x86/dumpstack: Print registers with the same log level as the backtrace Petr Mladek
2020-06-25 16:41 ` Dmitry Safonov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a0e7b79b-2ce7-f349-b308-e5329defd3fe@arista.com \
--to=dima@arista.com \
--cc=0x7f454c46@gmail.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®