From: Adam Simonelli <adamsimonelli@gmail.com>
To: 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>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH v7 3/3] tty: Change order of ttynull to be linked sooner if enabled as a console.
Date: Wed, 05 Mar 2025 23:32:09 -0500 [thread overview]
Message-ID: <8533590.alqRGMn8q6@nerdopolis2> (raw)
In-Reply-To: <CAHp75Ve02Ma1EswjnsxiV5uyh3A9NU0B90QLFGS13ifr594QFw@mail.gmail.com>
On Wednesday, March 5, 2025 2:22:06 PM EST Andy Shevchenko wrote:
> On Wed, Mar 5, 2025 at 6:30 AM <adamsimonelli@gmail.com> wrote:
> >
> > From: Adam Simonelli <adamsimonelli@gmail.com>
> >
> > If CONFIG_NULL_TTY_DEFAULT_CONSOLE is enabled, and CONFIG_VT is disabled,
> > ttynull will become the default primary console device, based on the link
> > order.
> >
> > Many distributions ship with CONFIG_VT enabled. On tested desktop hardware
> > if CONFIG_VT is disabled, the default console device falls back to
> > /dev/ttyS0 instead of /dev/tty.
> >
> > This could cause issues in user space, and hardware problems:
> >
> > 1. The user space issues include the case where /dev/ttyS0 is
> > disconnected, and the TCGETS ioctl, which some user space libraries use
> > as a probe to determine if a file is a tty, is called on /dev/console and
> > fails. Programs that call isatty() on /dev/console and get an incorrect
> > false value may skip expected logging to /dev/console.
> >
> > 2. The hardware issues include the case if a user has a science instrument
> > or other device connected to the /dev/ttyS0 port, and they were to upgrade
> > to a kernel that is disabling the CONFIG_VT option, kernel logs will then be
> > sent to the device connected to /dev/ttyS0 unless they edit their kernel
> > command line manually.
> >
> > The new CONFIG_NULL_TTY_CONSOLE option will give users and distribution
> > maintainers an option to avoid this. Disabling CONFIG_VT and enabling
> > CONFIG_NULL_TTY_CONSOLE will ensure the default kernel console behavior
> > is not dependant on hardware configuration by default, and avoid
> > unexpected new behavior on devices connected to the /dev/ttyS0 serial
> > port.
>
> ...
>
> Since it touches the link order only under drivers/tty the commit
> message should mention what the effect will be on the consoles drivers
> for which are located elsewhere.
>
>
OK, I will think of what to say. Based on what I tested in throwing a preferred
console in x86 though, it seems like ttynull was still at the top of the list
of /proc/consoles still, I just have to come up with a good way to mention that
in the commit message.
prev parent reply other threads:[~2025-03-06 4:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 4:29 [PATCH v7 0/3] Optionally allow ttynull to be selected as a default console adamsimonelli
2025-03-05 4:29 ` [PATCH v7 1/3] ttynull: Always initialize console index to -1 adamsimonelli
2025-03-05 4:29 ` [PATCH v7 2/3] ttynull: Add an option to allow ttynull to be used as a console device adamsimonelli
2025-03-05 19:18 ` Andy Shevchenko
2025-03-06 1:30 ` Adam Simonelli
2025-03-06 7:06 ` Andy Shevchenko
2025-03-06 13:41 ` Adam Simonelli
2025-03-05 4:29 ` [PATCH v7 3/3] tty: Change order of ttynull to be linked sooner if enabled as a console adamsimonelli
2025-03-05 19:22 ` Andy Shevchenko
2025-03-06 4:32 ` Adam Simonelli [this message]
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=8533590.alqRGMn8q6@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=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