From: Adam Simonelli <adamsimonelli@gmail.com>
To: Petr Mladek <pmladek@suse.com>,
John Ogness <john.ogness@linutronix.de>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiri Slaby <jirislaby@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v4 0/2] Optionally allow ttynull to be selected as a default console
Date: Sun, 23 Feb 2025 19:23:21 -0500 [thread overview]
Message-ID: <7410687.31r3eYUQgx@nerdopolis2> (raw)
In-Reply-To: <Z7uOsqky4Tw9J6QR@surfacebook.localdomain>
On Sunday, February 23, 2025 4:10:10 PM EST Andy Shevchenko wrote:
> Sun, Feb 23, 2025 at 03:44:54PM -0500, adamsimonelli@gmail.com kirjoitti:
> > From: Adam Simonelli <adamsimonelli@gmail.com>
> >
> > When switching to a CONFIG_VT=n world, at least on x86 systems,
> > /dev/console becomes /dev/ttyS0. This can cause some undesired effects.
> > /dev/console's behavior is now tied to the physical /dev/ttyS0, which when
> > disconnected can cause isatty() to fail when /dev/ttyS0 is disconnected,
> > and users who upgrade to a theoretical vt-less kernel from their
> > distribution who have a device such as a science instrument connected to
> > their /dev/ttyS0 port will suddenly see it receive kernel log messages.
> >
> > When the new CONFIG_NULL_TTY_CONSOLE option is turned on, this will allow
> > the ttynull device to be leveraged as the default console. Distributions
> > that had CONFIG_VT turned on before will be able to leverage this option
> > to where /dev/console is still backed by a psuedo device, avoiding these
> > issues, without needing to enable the entire VT subsystem.
>
> This rings a bell of the following
>
> https://lore.kernel.org/all/20201111135450.11214-1-pmladek@suse.com/
> https://lore.kernel.org/all/20210107164400.17904-1-pmladek@suse.com/
> https://lore.kernel.org/all/20210108114847.23469-1-pmladek@suse.com/
>
> I don't see any mention in the commit message about these, have you studied the
> cases? Will your change anyhow affect the described there?
>
>
I did see that sifting through commits, it looks kind of different though, as
that was to make ttynull more always on, and if I am understanding it correctly
it looks more of a last resort? I could be wrong, but I see it was attempted
and reverted because of conflicts on some hardware platforms?
The scope with this new patch set is much different, as it has to be manually
enabled on top of CONFIG_NULL_TTY, rather than assuming CONFIG_NULL_TTY is
enabled, and adding it to the list of preferred consoles. It is more for
Desktop configs that are looking to disable CONFIG_VT, but still want
/dev/console to not be a physical device by default.
next prev parent reply other threads:[~2025-02-24 0:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-23 20:44 [PATCH v4 0/2] Optionally allow ttynull to be selected as a default console adamsimonelli
2025-02-23 20:44 ` [PATCH v4 1/2] ttynull: Add an option to allow ttynull to be used as a console device adamsimonelli
2025-02-23 20:44 ` [PATCH v4 2/2] tty: Change order of ttynull to be linked sooner if enabled as a console adamsimonelli
2025-02-24 7:23 ` Greg Kroah-Hartman
2025-02-24 12:38 ` Adam Simonelli
2025-02-23 21:10 ` [PATCH v4 0/2] Optionally allow ttynull to be selected as a default console Andy Shevchenko
2025-02-24 0:23 ` Adam Simonelli [this message]
2025-02-24 7:19 ` 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=7410687.31r3eYUQgx@nerdopolis2 \
--to=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=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
/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