lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y/k66v01i5z3kFMG@ZenIV>
Date:   Fri, 24 Feb 2023 22:32:10 +0000
From:   Al Viro <viro@...iv.linux.org.uk>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Greg KH <gregkh@...uxfoundation.org>,
        Tharun Kumar P <tharunkumar.pasumarthi@...rochip.com>,
        Kumaravel Thiagarajan <kumaravel.thiagarajan@...rochip.com>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Jiri Slaby <jslaby@...e.cz>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Andrew Morton <akpm@...ux-foundation.org>,
        linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org
Subject: Re: [GIT PULL] TTY/Serial driver updates for 6.3-rc1

On Fri, Feb 24, 2023 at 01:30:58PM -0800, Linus Torvalds wrote:
> On Fri, Feb 24, 2023 at 1:24 PM Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
> >
> >         default SERIAL_8250
> 
> Hmm. Looking around, it seems to be a pattern. I'm not convinced any
> of them are really valid, except probably the ones that aren't about
> specific drivers, but about base support (like the "SERIAL_8250_DMA"
> one).
> 
> I also do get the feeling that the base "SERIAL_8250" feature might be
> better off as a _selected_ option, rather than a "ask if you want it".
> I think we've ended up with that SERIAL_8250 being a base option
> mainly for historical reasons (ie it was part of the original PC/AT
> base specs, and then later it has become a "base driver for a lot of
> random cards".
> 
> It's probably most legacy by now - it's a long time since I saw a
> serial port being used outside of management ports, and even those are
> often ethernet these days.

Serial console is hard to replace - sure, netconsole can take care of
the printk side of things, but the things like "boot with init=/bin/sh
and try to recover using that" are occasionally useful; same for "drop
into shell on initramfs and use that to poke around"...  What do you
use that kind of situations?  Not a rethorical question - I would be
really happy to know alternative variants for that; IME it's not
needed often (thankfully), but when it's needed it's really useful
to have...

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ