[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200527142649.aa3kgqvo2n4q4kyx@holly.lan>
Date: Wed, 27 May 2020 15:26:49 +0100
From: Daniel Thompson <daniel.thompson@...aro.org>
To: Sumit Garg <sumit.garg@...aro.org>
Cc: kgdb-bugreport@...ts.sourceforge.net, jason.wessel@...driver.com,
dianders@...omium.org, pmladek@...e.com,
sergey.senozhatsky@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/4] kdb: Check status of console prior to invoking
handlers
On Wed, May 27, 2020 at 11:55:57AM +0530, Sumit Garg wrote:
> Check if a console is enabled prior to invoking corresponding write
> handler.
>
> Suggested-by: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
> Signed-off-by: Sumit Garg <sumit.garg@...aro.org>
Reviewed-by: Daniel Thompson <daniel.thompson@...aro.org>
> ---
> kernel/debug/kdb/kdb_io.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/kernel/debug/kdb/kdb_io.c b/kernel/debug/kdb/kdb_io.c
> index f6b4d47..349dfcc 100644
> --- a/kernel/debug/kdb/kdb_io.c
> +++ b/kernel/debug/kdb/kdb_io.c
> @@ -564,6 +564,8 @@ static void kdb_msg_write(char *msg, int msg_len)
> kdb_io_write(msg, msg_len, dbg_io_ops->write_char);
>
> for_each_console(c) {
> + if (!(c->flags & CON_ENABLED))
> + continue;
> c->write(c, msg, msg_len);
> touch_nmi_watchdog();
> }
> --
> 2.7.4
>
Powered by blists - more mailing lists