Netdev List
 help / color / mirror / Atom feed
From: John Ogness <john.ogness@linutronix.de>
To: Sam Crossley <samuelcrossley@gmail.com>,
	Thomas Gleixner <tglx@kernel.org>,
	Breno Leitao <leitao@debian.org>, Petr Mladek <pmladek@suse.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>, Paolo Abeni <pabeni@redhat.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Simon Horman <horms@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-doc@vger.kernel.org,
	Sam Crossley <samuelcrossley@gmail.com>
Subject: Re: [PATCH RFC 0/2] netconsole: allow replaying the printk buffer on demand
Date: Mon, 26 Oct 2026 10:40:14 +0106	[thread overview]
Message-ID: <87fqxskdpl.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20261024-netcons-replay-upstream-v1-0-9613f38496e5@gmail.com>

On 2026-10-24, Sam Crossley <samuelcrossley@gmail.com> wrote:
> Netconsole only forwards records while an enabled target and its
> transport are available. A target enabled after boot, or one that was
> unreachable during a network outage, leaves a gap in the remote log that
> cannot currently be recovered.

This situation is no different than connecting a UART sometime after
boot, or having unplugged a serial cable temporarily during runtime.

> This adds a write-only "replay" attribute to the netconsole configfs
> subsystem that rewinds the netconsole consoles so the retained ring is
> re-sent.

I would prefer that we find a more general interface for this. One that
can apply to all consoles, not just netconsole.

We have a couple console features planned or in discussion: per-console
loglevels [0] and per-console unsafe dumping/ordering [1]. Both of these
are per-console, meaning they also involve the netconsole.

I think we need the netconsole to support a general console interface
rather than introducing netconsole-only knobs (particularly when such
features could be valid for any console).

In the per-console loglevel series Chris Down introduces [2]
/sys/class/console/ to sysfs. This is where we would put all the
upcoming per-console knobs. I would expect a replay trigger would fit
well there.

John Ogness

[0] https://lore.kernel.org/lkml/cover.1764272407.git.chris@chrisdown.name/
[1] https://lore.kernel.org/lkml/87bj8kkfwk.fsf@jogness.linutronix.de/
[2] https://lore.kernel.org/lkml/84b8d91693e56f6026271bc40553bcb6657ab24d.1764272407.git.chris@chrisdown.name/

  parent reply	other threads:[~2026-10-26  9:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-24 23:06 [PATCH RFC 0/2] netconsole: allow replaying the printk buffer on demand Sam Crossley
2026-10-24 23:06 ` [PATCH RFC 1/2] printk: add per-console replay helper Sam Crossley
2026-10-24 23:06 ` [PATCH RFC 2/2] netconsole: add configfs trigger to replay printk buffer Sam Crossley
2026-10-26  9:34 ` John Ogness [this message]
2026-10-26 11:44   ` [PATCH RFC 0/2] netconsole: allow replaying the printk buffer on demand Breno Leitao
2026-10-26 13:09     ` John Ogness
2026-10-26 14:58       ` Petr Mladek
2026-10-26 16:33         ` John Ogness
2026-10-26 17:49           ` Breno Leitao
2026-10-27 13:47             ` Petr Mladek
2026-10-27 15:54               ` Breno Leitao
2026-10-27 17:45                 ` Petr Mladek
2026-10-27 12:58           ` Petr Mladek
2026-10-26 14:39     ` Chris Down
2026-10-26 15:32       ` Breno Leitao

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=87fqxskdpl.fsf@jogness.linutronix.de \
    --to=john.ogness@linutronix.de \
    --cc=andrew+netdev@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pmladek@suse.com \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=samuelcrossley@gmail.com \
    --cc=senozhatsky@chromium.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tglx@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