Linux regressions report for mainline [2022-11-06]

[Regzbot (on behalf of Thorsten Leemhuis)]

Hi Linus! Below is a slightly edited report from regzbot listing all
regression from this cycle that the bot and I are currently aware of.

Patches for two mm issues are available. I guess Andrew will send
them your way in the next few days (one of them hasn't even hit -next yet).

The amdgpu issue is progressing slowly. The efi issue looks stalled,
will poke the thread tomorrow; maybe there was some progress and I just
missed it.

HTH, Ciao, Thorsten

---

Hi, this is regzbot, the Linux kernel regression tracking bot.

Currently I'm aware of 4 regressions in linux-mainline. Find the
current status below and the latest on the web:

https://linux-regtracking.leemhuis.info/regzbot/mainline/

Bye bye, hope to see you soon for the next report.
   Regzbot (on behalf of Thorsten Leemhuis)


======================================================
current cycle (v6.0.. aka v6.1-rc), culprit identified
======================================================


[ *NEW* ] mm/btrfs: systemd-oomd overreacting due to PSI changes for Btrfs
--------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/d20a0a85-e415-cf78-27f9-77dd7a94bc8d@xxxxxxxxxxxxx/
https://lore.kernel.org/linux-block/d20a0a85-e415-cf78-27f9-77dd7a94bc8d@xxxxxxxxxxxxx/

By Thorsten Leemhuis; 3 days ago; 5 activities, latest 2 days ago.
Introduced in 4088a47e78f9 (v6.1-rc1)

Recent activities from: Johannes Weiner (2), Thorsten Leemhuis (2),
  Christoph Hellwig (1)

2 patch postings are associated with this regression, the latest is this:
* Re: [REGESSION] systemd-oomd overreacting due to PSI changes for Btrfs (was: Re: [PATCH 3/5] btrfs: add manual PSI accounting for compressed reads)
  https://lore.kernel.org/linux-fsdevel/Y2UHRqthNUwuIQGS@xxxxxxxxxxx/
  2 days ago, by Johannes Weiner


mm: sparc64: dpkg fails on sparc64 since "mm/thp: Carry over dirty bit when thp splits on pmd)"
-----------------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/20221021160603.GA23307@xxxxxxxxxxxx/
https://lore.kernel.org/lkml/20221021160603.GA23307@xxxxxxxxxxxx/

By Anatoly Pugachev; 16 days ago; 8 activities, latest 2 days ago.
Introduced in 0ccf7f168e17 (v6.1-rc1)

Fix incoming:
* Partly revert "mm/thp: carry over dirty bit when thp splits on pmd"
  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=434e3d15d92b0be26e0acd7dbbeb75ca20d64a6c


drm: amdgpu: some games (Cyberpunk 2077, Forza Horizon 4/5) hang at start
-------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/CABXGCsOeQ7VYm98jRVaYp6KaNsFVsAnSb33ZT8JvZxcTcEGW0w@xxxxxxxxxxxxxx/
https://lore.kernel.org/lkml/CABXGCsOeQ7VYm98jRVaYp6KaNsFVsAnSb33ZT8JvZxcTcEGW0w@xxxxxxxxxxxxxx/

By Mikhail Gavrilov; 16 days ago; 8 activities, latest 4 days ago.
Introduced in dd80d9c8eeca (v6.1-rc1)

Recent activities from: Christian König (2), Mikhail Gavrilov (2)


efi: crashes due to broken runtime-wrapper
------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/CAMj1kXHDtwkMgqqwePEKdOdO=7-1_TYyuVNPJ7PkyreaMySjCw@xxxxxxxxxxxxxx/
https://lore.kernel.org/linux-arm-kernel/CAMj1kXHDtwkMgqqwePEKdOdO=7-1_TYyuVNPJ7PkyreaMySjCw@xxxxxxxxxxxxxx/

By Ard Biesheuvel; 9 days ago; 4 activities, latest 9 days ago.
Introduced in d3549a938b73 (v6.1-rc1)


=============
End of report
=============

All regressions marked '[ *NEW* ]' were added since the previous report,
which can be found here:
https://lore.kernel.org/r/166715973405.73686.12627284653277847588@xxxxxxxxxxxxx

Thanks for your attention, have a nice day!

  Regzbot, your hard working Linux kernel regression tracking robot


P.S.: Wanna know more about regzbot or how to use it to track regressions
for your subsystem? Then check out the getting started guide or the
reference documentation:

https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md

The short version: if you see a regression report you want to see
tracked, just send a reply to the report where you Cc
regressions@xxxxxxxxxxxxxxx with a line like this:

#regzbot introduced: v5.13..v5.14-rc1

If you want to fix a tracked regression, just do what is expected
anyway: add a 'Link:' tag with the url to the report, e.g.:

Link: https://lore.kernel.org/all/30th.anniversary.repost@xxxxxxxxxxxxxxxxxx/