mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: Breno Leitao <leitao@debian.org>,
	Ryan Roberts <ryan.roberts@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Rio <rioo.tsukatsukii@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v1] panic: Flush unsafe consoles before panic reboot
Date: Thu, 05 Nov 2026 20:01:38 +0100	[thread overview]
Message-ID: <87v76bf6gd.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <auyz7JPCK7K9QFT_@pathway.suse.cz>

On 2026-11-05, Petr Mladek <pmladek@suse.com> wrote:
>> And maybe users want safe drivers (such as 8250) to enter "hope and
>> pray mode" on kernel ending sites, which is something even legacy
>> consoles could not always do.
>
> I think that I finally understand your concern. You would like to
> add a per-console flag for "debugging" or "safe" mode. But
> it might be weird when:
>
>   + netconsole is in the "debugging" mode by default.
>
>   + other serial consoles are in the "safe" mode by default.

Yes. Although I would not call it "debugging" and "safe".

> I see two solutions:
>
>    1. Keep all NBCON consoles consistent and allow unsafe takeover
>       on more locations, independently whether they have safe
>       or unsafe write_atomic().
>
>    2. Allow the unsafe takeover on more locations only for netconsole.
>       And later allow to set both per-console policies: "debugging"
>       vs. "safe".  And accept that netconsole has different default
>       policy.
>
> I personally prefer the 2nd solution. Netconsole has always been
> a bit special. And maybe someone would implement the safe write_atomic
> in the future which will make it more normal, ...

I agree. I am preparing a patch that should allow exactly that and
hopefully make my idea with the policies clear.

John

  reply	other threads:[~2026-11-05 19:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 10:01 Ryan Roberts
2026-09-15 10:06 ` Ryan Roberts
2026-09-15 18:49   ` Bradley Morgan
2026-09-16  7:44     ` Ryan Roberts
2026-09-16 14:58       ` Bradley Morgan
2026-09-16 13:08 ` Petr Mladek
2026-10-22 20:35   ` Gustavo Luiz Duarte
2026-10-23  7:57   ` John Ogness
2026-10-23 10:36     ` Petr Mladek
2026-10-27 16:12       ` Breno Leitao
2026-10-27 17:43         ` Breno Leitao
2026-10-27 18:01           ` John Ogness
2026-10-28 11:24             ` Breno Leitao
2026-10-28 10:52     ` Breno Leitao
2026-10-28 14:37       ` John Ogness
2026-10-28 21:15         ` Breno Leitao
2026-10-29  9:20           ` John Ogness
2026-10-29 10:58             ` Breno Leitao
2026-10-29 13:53               ` John Ogness
2026-10-29 14:37                 ` Petr Mladek
2026-10-30 17:56                   ` Breno Leitao
2026-11-02 10:28                     ` Petr Mladek
2026-11-02 13:27                       ` Breno Leitao
2026-11-02 22:22                       ` John Ogness
2026-11-03 13:31                         ` Petr Mladek
2026-11-04 11:18                           ` John Ogness
2026-11-05 16:50                             ` Petr Mladek
2026-11-05 19:01                               ` John Ogness [this message]
2026-11-02 22:14                     ` John Ogness

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=87v76bf6gd.fsf@jogness.linutronix.de \
    --to=john.ogness@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=rioo.tsukatsukii@gmail.com \
    --cc=rostedt@goodmis.org \
    --cc=ryan.roberts@arm.com \
    --cc=senozhatsky@chromium.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®