linux-kernel - Re: Regression in kernel 6.8.2 fails in various ways (USB, BT, ...)

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: <20240407103434.GA31628@reaktio.net>
Date: Sun, 7 Apr 2024 13:34:34 +0300
From: Pasi Kärkkäinen <pasik@....fi>
To: Oleksandr Natalenko <oleksandr@...alenko.name>
Cc: linux-kernel@...r.kernel.org, Norbert Preining <norbert@...ining.info>,
	stable@...r.kernel.org, regressions@...mhuis.info
Subject: Re: Regression in kernel 6.8.2 fails in various ways (USB, BT, ...)

On Sun, Apr 07, 2024 at 12:44:58PM +0300, Pasi Kärkkäinen wrote:
> On Sun, Apr 07, 2024 at 12:39:31PM +0300, Pasi Kärkkäinen wrote:
> > > > 
> > > > I noticed possible related USB problem/regression also with Linux 6.7.11, eg. my USB headset is not detected at all anymore when running Linux 6.7.11. USB headset works OK with Linux 6.7.9, so the regression is included/backported to also either in 6.7.10 or in 6.7.11.
> > > 
> > > It wound be nice to narrow this range down even further with bisection because there are too many changes between v6.7.9 and v6.7.11 that could cause this.
> > > 
> > 
> > I just tested more Fedora kernel rpms, and it seems Linux 6.7.10 still works OK,
> > but 6.7.11 has the regression (eg. USB devices not detected, laptop does not reboot 
> > as it gets stuck before resetting the machine).
> > 
> > So the regression was backported to Linux 6.7.11.
> > 
> 
> And with more testing interestingly it seems Linux 6.7.12 already fixes the problem.
> 
> I tried multiple times: 6.7.10 works, 6.7.11 doesn't, and 6.7.12 again works.
> 

Looking at the Linux 6.7.x changelogs I'm *guessing* it's these commits:


6.7.11 (broken):

commit 963b977bc4204cc1dcc0c190d1ba255aa5c5dd19
Author: Sean Anderson <sean.anderson@...o.com>
Date:   Tue Jan 23 17:51:09 2024 -0500

    usb: phy: generic: Get the vbus supply
    
    [ Upstream commit 75fd6485cccef269ac9eb3b71cf56753341195ef ]
    
    While support for working with a vbus was added, the regulator was never
    actually gotten (despite what was documented). Fix this by actually
    getting the supply from the device tree.
    
    Fixes: 7acc9973e3c4 ("usb: phy: generic: add vbus support")
    Signed-off-by: Sean Anderson <sean.anderson@...o.com>
    Link: https://lore.kernel.org/r/20240123225111.1629405-3-sean.anderson@seco.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
    Signed-off-by: Sasha Levin <sashal@...nel.org>


6.7.12 (working):

commit fc3b5406b75472e1353073d1f410421aed62b793
Author: Alexander Stein <alexander.stein@...tq-group.com>
Date:   Thu Mar 14 10:26:27 2024 +0100

    Revert "usb: phy: generic: Get the vbus supply"
    
    commit fdada0db0b2ae2addef4ccafe50937874dbeeebe upstream.
    
    This reverts commit 75fd6485cccef269ac9eb3b71cf56753341195ef.
    This patch was applied twice by accident, causing probe failures.
    Revert the accident.
    
    Signed-off-by: Alexander Stein <alexander.stein@...tq-group.com>
    Fixes: 75fd6485ccce ("usb: phy: generic: Get the vbus supply")
    Cc: stable <stable@...nel.org>
    Reviewed-by: Sean Anderson <sean.anderson@...o.com>
    Link: https://lore.kernel.org/r/20240314092628.1869414-1-alexander.stein@ew.tq-group.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>



-- Pasi