linux-kernel - Re: Linux regressions report for mainline [2024-06-30]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <b546d9e0-b52f-4b64-8247-3c85026f3b36@leemhuis.info>
Date: Fri, 5 Jul 2024 20:15:34 +0200
From: Thorsten Leemhuis <regressions@...mhuis.info>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
 Linux regressions mailing list <regressions@...ts.linux.dev>
Subject: Re: Linux regressions report for mainline [2024-06-30]

On 30.06.24 18:13, Regzbot (on behalf of Thorsten Leemhuis) wrote:
> Hi Linus, find below the weekly report for regressions introduced
> during this cycle. Overall it does not look to bad, but a bit worse then
> in the recent cycles. But there are a few discussions I will prod
> tomorrow to hopefully get a few of those resolved before -rc7; I might
> CC you on some of those threads if no resolution comes into sight soon.

Hi Linus, as -rc7 is due, here is a quick "extra" report in case you
want to know about regressions for which fixes already exist, that might
or might not make it to you during the next week.

* It seems the following compile fix fall through the cracks somewhat,
as it is only queued for -next:
https://lore.kernel.org/bpf/363ad8d1-a2d2-4fca-b66a-3d838eb5def9@intel.com/

  It fixes a compile problem that was apparently introduced this cycle.
This was recently brought up on the list, but seems nothing happened
since then; someone else complained about this problem to me in the
Fediverse today, too.
https://lore.kernel.org/all/d0dd2457-ab58-1b08-caa4-93eaa2de221e@nerdbynature.de/



* The following fix for f3d9683346d6 ("drm/bridge: adv7511: Allow IRQ to
share GPIO pins") took a while to get reviewed, but with a bit of luck
will be picked up by the drm subsystem soon and make it to you next week:
https://lore.kernel.org/lkml/20240630221931.1650565-1-aford173@gmail.com/


Ohh, and btw: the following fix for a 6.9 regression affecting arm
MMUless devices is also slowly progressing; not sure if someone will
finally pick this up next week:
https://lore.kernel.org/all/20240611100947.32241-1-yangyj.ee@gmail.com/

Ciao, Thorsten