Linux regressions report for mainline [2023-10-15]

[Regzbot (on behalf of Thorsten Leemhuis)]

Hi Linus. My list of unresolved regressions introduced during this cycle
got a lot shorter, as quite a few fixes for tracked issues found their
way into mainline over the past few days.

But there is one regression where things looked stalled despite the
following fix existing for a while:

https://lore.kernel.org/netdev/20230927055246.121544-1-xuanzhuo@xxxxxxxxxxxxxxxxx/

That fix was posted two and a half weeks ago (one day after the
regression linked in the patch description was reported) and got one ACK
one week ago; but apart for that nothing has happened afaics. Not sure
what's up there.

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.5.. aka v6.6-rc), culprit identified
======================================================


[ *NEW* ] Re:block: Fix regression in sed-opal for a saved key.
---------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/lore/53755a0fbd6318d4783078259f2d2f8ab5f2f0b7.camel@xxxxxxxxxxxxxxxxxx/
https://lore.kernel.org/lkml/53755a0fbd6318d4783078259f2d2f8ab5f2f0b7.camel@xxxxxxxxxxxxxxxxxx/

By Greg Joyce; 9 days ago; 3 activities, latest 1 days ago.
Introduced in 3bfeb6125664 (v6.6-rc1)

Fix incoming:
* block: Fix regression in sed-opal for a saved key.
  https://lore.kernel.org/lkml/2519b67c-58d3-4f87-9513-5321b1722b60@xxxxxxxxxxxxx/


Regression: devcoredump patch broke Realtek usb bluetooth adapter
-----------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/lore/20231003182038.k57nirtt4sonvt7c@xxxxxxxxxxxxxxxxx/
https://lore.kernel.org/lkml/20231003182038.k57nirtt4sonvt7c@xxxxxxxxxxxxxxxxx/

By Kirill A. Shutemov; 11 days ago; 12 activities, latest 1 days ago.
Introduced in 044014ce85a1 (v6.6-rc1)

Fix incoming:
* Bluetooth: btrtl: Ignore error return for hci_devcd_register()
  https://lore.kernel.org/lkml/b96190f1-44f4-4562-9030-6916e97c8b82@xxxxxxxxxxxxx/


powerpc: new page table range API causes PowerMac G5 to fail booting
--------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/lore/20230929132750.3cd98452@yea/
https://lore.kernel.org/linuxppc-dev/20230929132750.3cd98452@yea/

By Erhard Furtner; 16 days ago; 12 activities, latest 2 days ago.
Introduced in 9fee28baa601 (v6.6-rc1)

Recent activities from: Erhard Furtner (2), Michael Ellerman (2)

2 patch postings are associated with this regression, the latest is this:
* Re: [Bisected] PowerMac G5 fails booting kernel 6.6-rc3 (BUG: Unable to handle kernel data access at 0xfeffbb62ffec65fe)
  https://lore.kernel.org/linuxppc-dev/87mswwnec1.fsf@xxxxxxxxxxxxx/
  9 days ago, by Aneesh Kumar K.V


virtio: network-related regression when using SWIOTLB in the guest
------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/lore/20230926130451.axgodaa6tvwqs3ut@xxxxxxx/
https://lore.kernel.org/lkml/20230926130451.axgodaa6tvwqs3ut@xxxxxxx/

By Michael Roth; 18 days ago; 5 activities, latest 7 days ago.
Introduced in 295525e29a (v6.6-rc1)

Fix incoming:
* virtio_net: fix the missing of the dma cpu sync
  https://lore.kernel.org/lkml/a7a2bf25-cfc1-47a8-baf4-487a8574fb5a@xxxxxxxxxxxxx/


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

All regressions marked '[ *NEW* ]' were added since the previous report,
which can be found here:
https://lore.kernel.org/r/169678126224.160034.5275230285223450822@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/