public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: adamsimonelli@gmail.com
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jiri Slaby <jirislaby@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	John Ogness <john.ogness@linutronix.de>,
	Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCH v8 2/4] ttynull: Add an option to allow ttynull to be used as a console device
Date: Wed, 12 Mar 2025 16:37:07 +0100	[thread overview]
Message-ID: <Z9GqI2HvOJaAOr-r@pathway.suse.cz> (raw)
In-Reply-To: <20250311033133.1859963-3-adamsimonelli@gmail.com>

On Mon 2025-03-10 23:31:31, adamsimonelli@gmail.com wrote:
> From: Adam Simonelli <adamsimonelli@gmail.com>
> 
> The new config option, CONFIG_NULL_TTY_DEFAULT_CONSOLE will allow
> ttynull to be initialized by console_initcall() and selected as a
> possible console device.

It would be great to mention here the motivation. It is nicely
explained in the 3rd patch.

> --- a/drivers/tty/Kconfig
> +++ b/drivers/tty/Kconfig
> @@ -383,7 +383,20 @@ config NULL_TTY
>  	  available or desired.
>  
>  	  In order to use this driver, you should redirect the console to this
> -	  TTY, or boot the kernel with console=ttynull.
> +	  TTY, boot the kernel with console=ttynull, or enable
> +	  NULL_TTY_DEFAULT_CONSOLE.
> +
> +	  If unsure, say N.
> +
> +config NULL_TTY_DEFAULT_CONSOLE
> +	bool "Support for console on ttynull"
> +	depends on NULL_TTY=y && !VT_CONSOLE
> +	help
> +	  Say Y here if you want the NULL TTY to be used as a /dev/console
> +	  device.

I would provide few more details, something like:

<proposal>
	  Say Y here if you want the NULL TTY to be used as a /dev/console
	  device by default.

	  For example, it might be useful to prevent a VT-less kernel from
	  writing the system log to a random device connected to
	  the serial port.

	  Another console driver still might get preferred via the command line,
	  SPCR, or the device tree.
</proposal>

> +	  This is similar to VT_CONSOLE, but without the dependency on VT.
> +	  It uses the ttynull driver as the system console.

Honestly, I do not find this paragraph much useful. I would omit it,

>  	  If unsure, say N.
>  
> diff --git a/drivers/tty/ttynull.c b/drivers/tty/ttynull.c
> index d8b51edde628..67aad3e6f538 100644
> --- a/drivers/tty/ttynull.c
> +++ b/drivers/tty/ttynull.c
> @@ -96,6 +96,19 @@ static int __init ttynull_init(void)
>  	return 0;
>  }
>  
> +#ifdef CONFIG_NULL_TTY_DEFAULT_CONSOLE
> +static int __init ttynull_register(void)
> +{
> +	if (console_set_on_cmdline)
> +		return 0;
> +
> +	add_preferred_console("ttynull", 0, NULL);
> +
> +	return 0;
> +}
> +console_initcall(ttynull_register);
> +#endif

I have realized that this does not work without shuffling the linking
order (3rd patch).

I would prefer to avoid the linking order hack and rather call this
in console_init() directly, see
https://lore.kernel.org/r/Z9GPVVTnngGbmbuv@pathway.suse.cz
for more details.

Best Regards,
Petr

  reply	other threads:[~2025-03-12 15:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11  3:31 [PATCH v8 0/4] Optionally allow ttynull to be selected as a default console adamsimonelli
2025-03-11  3:31 ` [PATCH v8 1/4] ttynull: Always initialize console index to -1 adamsimonelli
2025-03-12 14:38   ` Petr Mladek
2025-03-13 12:09     ` Adam Simonelli
2025-03-11  3:31 ` [PATCH v8 2/4] ttynull: Add an option to allow ttynull to be used as a console device adamsimonelli
2025-03-12 15:37   ` Petr Mladek [this message]
2025-03-11  3:31 ` [PATCH v8 3/4] tty: Change order of ttynull to be linked sooner if enabled as a console adamsimonelli
2025-03-11  3:31 ` [PATCH v8 4/4] Documentation/serial-console: Document CONFIG_NULL_TTY_DEFAULT_CONSOLE adamsimonelli
2025-03-12 15:40   ` Petr Mladek
2025-03-11 19:50 ` [PATCH v8 0/4] Optionally allow ttynull to be selected as a default console Andy Shevchenko

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=Z9GqI2HvOJaAOr-r@pathway.suse.cz \
    --to=pmladek@suse.com \
    --cc=adamsimonelli@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --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