Hi Linus. Nothing much to report for mainline, all business as usual. I
had hoped Mauro would sent a pull with the media fixes, as they would
contain one fix[1] for a bug that at least two people hit, but I guess
it can wait another week.
Ohh, and in case you care: the Logitech HID bug[3] from the 6.3 cycle
was not really fixed[4] by commit 6199d23c91c or we dealt with two
problems all the time (I guess it's the latter). But that will take a
few days to sort out.
[1] 14b4bd01f8e ("media: verisilicon: Additional fix for the crash when
opening the driver")
[2] https://lore.kernel.org/lkml/4995215.LvFx2qVVIh@bagend/ and
https://lore.kernel.org/all/[email protected]/
[3] https://bugzilla.kernel.org/show_bug.cgi?id=217412
[4] https://bugzilla.kernel.org/show_bug.cgi?id=217523
Ciao, Thorsten
---
Hi, this is regzbot, the Linux kernel regression tracking bot.
Currently I'm aware of 9 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.3.. aka v6.4-rc), culprit identified
======================================================
[ *NEW* ] rcu: "spinlock bad magic" BUG when the SRCU notifier was ever used
----------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/[email protected]/
https://lore.kernel.org/lkml/[email protected]/
By Jon Hunter; 3 days ago; 10 activities, latest 0 days ago.
Introduced in 95433f726301 (v6.4-rc1)
Fix incoming:
* notifier: Initialize new struct srcu_usage field
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=cf193e74990d3b66d8b1c07232b8d42b316529ae
[ *NEW* ] Networking pull for v6.4 causes full system lockup on RTL8111/8168/8411
---------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/217519/
https://bugzilla.kernel.org/show_bug.cgi?id=217519
https://lore.kernel.org/lkml/[email protected]/
By SamW and SamW; 2 days ago; 6 activities, latest 1 days ago.
Introduced in 6e98b09da931 (v6.4-rc1)
Recent activities from: SamW (3), Bagas Sanjaya (2), Heiner Kallweit (1)
[ *NEW* ] USB typec quirk for Asus Zenbook UM325 triggers system freeze on Acer ConceptD 7
------------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/217517/
https://bugzilla.kernel.org/show_bug.cgi?id=217517
https://lore.kernel.org/lkml/[email protected]/
By Stephan Bolten and Stephan Bolten; 2 days ago; 5 activities, latest 1 days ago.
Introduced in 326e1c208f3f (v6.4-rc1)
Recent activities from: Stephan Bolten (4), Heikki Krogerus (1)
One patch associated with this regression:
* bugzilla.kernel.org bug 217517: new comment(#1)
https://bugzilla.kernel.org/show_bug.cgi?id=217517#c1
1 days ago, by Heikki Krogerus
regulator: qcom-rpmh: Dragonboard 845c broken due to asynchronous probe
-----------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/CAMi1Hd1avQDcDQf137m2auz2znov4XL8YGrLZsw5edb-NtRJRw@mail.gmail.com/
https://lore.kernel.org/lkml/CAMi1Hd1avQDcDQf137m2auz2znov4XL8YGrLZsw5edb-NtRJRw@mail.gmail.com/
By Amit Pundir; 21 days ago; 22 activities, latest 1 days ago.
Introduced in ad44ac082fd (v6.4-rc1)
Recent activities from: Amit Pundir (7), Mark Brown (2), Doug
Anderson (1)
One patch associated with this regression:
* Re: [PATCH] regulator: qcom-rpmh: Revert "regulator: qcom-rpmh: Use PROBE_FORCE_SYNCHRONOUS"
https://lore.kernel.org/lkml/[email protected]/
20 days ago, by Caleb Connolly
Noteworthy links:
* [PATCH] Revert "regulator: qcom-rpmh: Revert "regulator: qcom-rpmh: Use PROBE_FORCE_SYNCHRONOUS""
https://lore.kernel.org/lkml/[email protected]/
19 days ago, by Amit Pundir; thread monitored.
* [PATCH] arm64: dts: qcom: sdm845-db845c: Move LVS regulator nodes up
https://lore.kernel.org/lkml/[email protected]/
1 days ago, by Amit Pundir; thread monitored.
[ *NEW* ] media: dvb-core: DVB card sometimes does not initialize
-----------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/[email protected]/
https://lore.kernel.org/lkml/[email protected]/
By Thomas Voegtle; 5 days ago; 1 activities, latest 5 days ago.
Introduced in 6769a0b7ee0c (v6.4-rc3)
Recent activities from: Thomas Voegtle (1)
[ *NEW* ] media: verisilicon: null pointer dereference in try_fmt
-----------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/4995215.LvFx2qVVIh@bagend/
https://lore.kernel.org/lkml/4995215.LvFx2qVVIh@bagend/
https://lore.kernel.org/lkml/[email protected]/
By Diederik de Haas and Benjamin Gaignard; 15 days ago; 8 activities, latest 5 days ago.
Introduced in db6f68b51e5c (v6.4-rc1)
Fix incoming:
* media: verisilicon: Additional fix for the crash when opening the driver
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=14b4bd01f8e5d663a41ef8cec5857db874b66e88
=============
End of report
=============
All regressions marked '[ *NEW* ]' were added since the previous report,
which can be found here:
https://lore.kernel.org/r/[email protected]
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
[email protected] 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/[email protected]/
Em Sun, 4 Jun 2023 12:13:57 +0000
"Regzbot (on behalf of Thorsten Leemhuis)" <[email protected]> escreveu:
> Hi Linus. Nothing much to report for mainline, all business as usual. I
> had hoped Mauro would sent a pull with the media fixes, as they would
> contain one fix[1] for a bug that at least two people hit, but I guess
> it can wait another week.
>
> Ohh, and in case you care: the Logitech HID bug[3] from the 6.3 cycle
> was not really fixed[4] by commit 6199d23c91c or we dealt with two
> problems all the time (I guess it's the latter). But that will take a
> few days to sort out.
>
> [1] 14b4bd01f8e ("media: verisilicon: Additional fix for the crash when
> opening the driver")
We opted to use a different approach for the same bug [1]:
14b4bd01f8e5 ("media: verisilicon: Additional fix for the crash when opening the driver")
[1] https://lore.kernel.org/linux-media/[email protected]/T/
Patch is already at linux-next. I'm sending the pull request in
a few, together with other fixes.
I was planning to send this earlier, but I got sick and had to take
some days off to recover my health.
Regards,
Mauro