[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YhRGI51mOEy2EAZb@google.com>
Date: Tue, 22 Feb 2022 11:10:43 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: "Guilherme G. Piccoli" <gpiccoli@...lia.com>,
linux-kernel@...r.kernel.org, bhe@...hat.com, pmladek@...e.com,
akpm@...ux-foundation.org, anton@...msg.org, ccross@...roid.com,
dyoung@...hat.com, feng.tang@...el.com, john.ogness@...utronix.de,
keescook@...omium.org, kernel@...ccoli.net,
kexec@...ts.infradead.org, rostedt@...dmis.org,
tony.luck@...el.com, vgoyal@...hat.com
Subject: Re: [PATCH V6] panic: Move panic_print before kmsg dumpers
A trivial typo:
On (22/02/22 11:06), Sergey Senozhatsky wrote:
> @@ -286,6 +289,8 @@ void panic(const char *fmt, ...)
> */
> atomic_notifier_call_chain(&panic_notifier_list, 0, buf);
>
>
> + panic_print_sys_info(panic_print & ~PANIC_PRINT_ALL_PRINTK_MSG);
>
>
> kmsg_dump(KMSG_DUMP_PANIC);
>
> /*
> @@ -316,7 +321,7 @@ void panic(const char *fmt, ...)
> debug_locks_off();
> console_flush_on_panic(CONSOLE_FLUSH_PENDING);
>
+ panic_print_sys_info(panic_print & PANIC_PRINT_ALL_PRINTK_MSG);
I also wonder if we want to CONSOLE_FLUSH_PENDING when
PANIC_PRINT_ALL_PRINTK_MSG set.
Powered by blists - more mailing lists