From: Daniel Vetter <firstname.lastname@example.org>
To: Geert Uytterhoeven <email@example.com>
Cc: Linus Torvalds <firstname.lastname@example.org>,
Phillip Susi <email@example.com>, Pavel Machek <firstname.lastname@example.org>,
Randy Dunlap <email@example.com>,
Greg Kroah-Hartman <firstname.lastname@example.org>,
Linux Fbdev development list <email@example.com>
Subject: Re: fbcon: remove soft scrollback code (missing Doc. patch)
Date: Thu, 14 Jan 2021 17:11:07 +0100 [thread overview]
Message-ID: <CAKMK7uEwHu5GLF16wn83PLZUjoJWgF0dcLXwsGkt_aBpOgLtfirstname.lastname@example.org> (raw)
On Thu, Jan 14, 2021 at 4:56 PM Geert Uytterhoeven <email@example.com> wrote:
> Hi Daniel,
> CC linux-fbdev
> On Tue, Jan 12, 2021 at 5:00 PM Daniel Vetter <firstname.lastname@example.org> wrote:
> > On Sat, Jan 9, 2021 at 12:11 AM Linus Torvalds
> > <email@example.com> wrote:
> > > On Fri, Jan 8, 2021 at 11:13 AM Phillip Susi <firstname.lastname@example.org> wrote:
> > > > > Could we pause this madness? Scrollback is still useful. I needed it
> > > > > today... it was too small, so command results I was looking for
> > > > > already scrolled away, but... life will be really painful with 0
> > > > > scrollback.
> > > >
> > > > > You'll need it, too... as soon as you get oops and will want to see
> > > > > errors just prior to that oops.
> > > >
> > > > > If it means I get to maintain it... I'm not happy about it but that's
> > > > > better than no scrollback.
> > > >
> > > > Amen! What self respecting admin installs a gui on servers? What do we
> > > > have to do to get this back in? What was so buggy with this code that
> > > > it needed to be removed? Why was it such a burden to just leave it be?
> > >
> > > It really was buggy, with security implications. And we have no maintainers.
> > >
> > > So the scroll-back code can't come back until we have a maintainer and
> > > a cleaner and simpler implementation.
> > >
> > > And no, maintaining it really doesn't mean "just get it back to the
> > > old broken state".
> > >
> > > So far I haven't actually seen any patches, which means that it's not
> > > coming back.
> > >
> > > The good news? If you have an actual text VGA console, that should
> > > still work just fine.
> IIRC, all of this was written for systems lacking VGA text consoles
> in the first place...
> > Also on anything that is remotely modern (i.e. runs a drm kernel
> > modesetting driver undearneath the fbdev/fbcon stack) there's a pile
> > more issues on top of just the scrollback/fbcon code being a mess.
> Would it help to remove DRM_FBDEV_EMULATION (instead)?
It's a problem with the hardware. "Write some registers and done"
isn't how display blocks work nowadays. So your proposal amounts to
"no fbdev/fbcon for anything modern-ish".
Also I said "a pile more", most of the issues in fbcon/fbdev code
apply for all drivers.
> > Specifically the locking is somewhere between yolo and outright
> > deadlocks. This holds even more so if the use case here is "I want
> > scrollback for an oops". There's rough sketches for how it could be
> > solved, but it's all very tricky work.
> When an oops happens, all bets are off. At that point, all information
> you can extract from the system is valuable, and additional locking
> issues are moot.
Except the first oops then scrolls aways because it's getting buried
under further fail. Your locking needs to be minimally good enough to
not make the situation worse.
> > Also adding dri-devel since defacto that's the only place where
> > display people hang out nowadays.
> Please keep on CCing linux-fbdev, especially for patches removing
> fbdev features.
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- email@example.com
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
Software Engineer, Intel Corporation
next prev parent reply other threads:[~2021-01-14 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200916205434.GA10389@duo.ucw.cz>
[not found] ` <firstname.lastname@example.org>
[not found] ` <CAHk-=wjsjC1h7fskwYaaRLykN1ms6ZtxGvucQgmL-zZTfxPdBA@mail.gmail.com>
[not found] ` <CAKMK7uEGXOC_ci=Drm=Hz+xPGdcoxv8YZ-gcOckoPmu2XijiSA@mail.gmail.com>
2021-01-14 15:56 ` fbcon: remove soft scrollback code (missing Doc. patch) Geert Uytterhoeven
2021-01-14 16:11 ` Daniel Vetter [this message]
2021-01-15 8:06 ` Geert Uytterhoeven
2021-02-03 8:03 ` Thomas Zimmermann
2021-01-22 18:55 ` Phillip Susi
2021-01-25 15:39 ` Geert Uytterhoeven
2021-02-02 14:18 ` Daniel Vetter
2021-02-02 15:13 ` Phillip Susi
2021-02-02 15:23 ` Daniel Vetter
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).