Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 16 Mar 2020 14:35:17 -0400
From:   Steven Rostedt <rostedt@goodmis.org>
To:     Eugeniu Rosca <roscaeugeniu@gmail.com>
Cc:     linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>,
        Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
        Ingo Molnar <mingo@kernel.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        Peter Zijlstra <peterz@infradead.org>,
        Jisheng Zhang <Jisheng.Zhang@synaptics.com>,
        Valdis Kletnieks <valdis.kletnieks@vt.edu>,
        Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
        Andrew Gabbasov <andrew_gabbasov@mentor.com>,
        Dirk Behme <dirk.behme@de.bosch.com>,
        Eugeniu Rosca <erosca@de.adit-jv.com>
Subject: Re: [RFC PATCH 0/3] Fix quiet console in pre-panic scenarios
Message-ID: <20200316143517.651abbeb@gandalf.local.home>
In-Reply-To: <20200315170903.17393-1-erosca@de.adit-jv.com>
References: <20200315170903.17393-1-erosca@de.adit-jv.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Sun, 15 Mar 2020 18:09:00 +0100
Eugeniu Rosca <roscaeugeniu@gmail.com> wrote:

> Dear community,
> 
> The motivation behind this seris is to save days/weeks, if not months,
> of debugging efforts for users who:
> 
>  * experience an issue like softlockup/hardlockup/hung task/oom, whose
>    reproduction is not clear and whose occurrence rate is very low
>  * are constrained to use a low loglevel value (1,2,3) in production
>  * mostly rely on console logs to debug the issue post-mortem
>    (e.g. saved to persistent storage via e.g. pstore)
> 
> As pointed out in the last patch from this series, under the above
> circumstances, users might simply lack any relevant logs during
> post-mortem analysis.
> 
> Why this series is marked as RFC is because:
>  * There are several possible approaches to turn console verbosity on
>    and off. Current series employs the 'ignore_loglevel' functionality,
>    but an alternative way is to use the 'console_loglevel' variable. The
>    latter is more intrusive, hence the former has been chosen as v1.
>  * Manipulating 'ignore_loglevel' might be seen as an abuse, especially
>    because it breaks the expectation of users who assume the system to
>    be dead silent after passing loglevel=0 on kernel command line.
> 
> Thank you for your comments!

I don't see any issues with this patch set. What do others think?

Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>

[ Note, I only acked, and did not give a deep review of it ]

-- Steve

> 
> Eugeniu Rosca (3):
>   printk: convert ignore_loglevel to atomic_t
>   printk: add console_verbose_{start,end}
>   watchdog: Turn console verbosity on when reporting softlockup
> 
>  include/linux/printk.h | 10 ++++++++++
>  kernel/printk/printk.c | 30 ++++++++++++++++++++++++++----
>  kernel/watchdog.c      |  4 ++++
>  3 files changed, 40 insertions(+), 4 deletions(-)
>