From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Regzbot (on behalf of Thorsten Leemhuis)"
<regressions@leemhuis.info>, Huacai Chen <chenhuacai@kernel.org>,
Javier Martinez Canillas <javierm@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: Linux regressions report for mainline [2023-10-29]
Date: Sun, 29 Oct 2023 07:19:03 -1000 [thread overview]
Message-ID: <CAHk-=wgEHNFHpcvnp2X6-fjBngrhPYO=oHAR905Q_qk-njV31A@mail.gmail.com> (raw)
In-Reply-To: <169858752781.1095326.10615907253726224231@leemhuis.info>
On Sun, 29 Oct 2023 at 03:52, Regzbot (on behalf of Thorsten Leemhuis)
<regressions@leemhuis.info> wrote:
>
> One of the remaining ones is new:
> module loading trouble on some laptops. Not nice, but likely nothing
> many users will encounter. The quota compilation oddity problem from
> Andy is also still around (unless it was fixed without me noticing); and
> a memleak, too.
The quota thing remains unexplained, and honestly seems like a timing
issue that just happens to hit Andy. Very strange, but I suspect that
without more reports (that may or may not ever happen), we're stuck.
> * There was another report about a blank screen during boot on a Lenovo
> laptop because simpledrm (that users apparently had enabled without
> problems beforehand) started to support those machines due to
> 60aebc9559492c ("drivers/firmware: Move sysfb_init() from
> device_initcall to subsys_initcall_sync"). I suggested a revert, but the
> developers disagree (to quote: "From my point of view, this is not a
> regression, 60aebc9559492c doesn't cause a problem, but exposes a
> problem.")
Honestly, "exposes a problem" is pretty much the *definition* of a
regression. So that excuse is particularly bad.
The whole point of "regression" is "things that used to work no longer work".
And no, "there's another bug that needs to be fixed" is _not_ the
answer - not unless you have that fix in hand.
That said, this already went into 6.5, so I'm not going to revert it
now just before the 6.6 release. That would be more dangerous than
just letting things be. But yes, a revert is likely the right thing to
do, unless people have figured out what is wrong with simplefb.
Linus
next prev parent reply other threads:[~2023-10-29 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 13:52 Linux regressions report for mainline [2023-10-29] Regzbot (on behalf of Thorsten Leemhuis)
2023-10-29 17:19 ` Linus Torvalds [this message]
2023-10-30 2:18 ` Huacai Chen
2023-10-30 2:52 ` Linus Torvalds
2023-10-30 3:10 ` Huacai Chen
2023-10-30 15:49 ` Thorsten Leemhuis
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='CAHk-=wgEHNFHpcvnp2X6-fjBngrhPYO=oHAR905Q_qk-njV31A@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=chenhuacai@kernel.org \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.