Bug#1032948: linux-image-6.1.0-5-amd64: oops in ucsi_acpi_notify
Control: tag -1 upstream fixed-upstream patch
On Tue, Apr 4, 2023 at 22:03:28 +0200, Diederik de Haas wrote:
> On Tuesday, 4 April 2023 13:11:16 CEST Julien Cristau wrote:
> > On Mon, Apr 3, 2023 at 15:16:42 +0200, Diederik de Haas wrote:
> > > On Saturday, 18 March 2023 23:10:39 CEST Diederik de Haas wrote:
> > >
> > > On Monday, 3 April 2023 14:57:02 CEST Julien Cristau wrote:
> > > > > Not sure why patchwork still shows v2 of the patch as v4 is available
> > > > > here:
> > > > > https://lore.kernel.org/all/20230308154244.722337-1-hdegoede@redhat.com/
> > > >
> > > > I'll give the patch series you linked in the other reply a go now.
> > >
> > > FTR: 2 out of the 3 patches have landed in 6.1.22
> >
> > Thanks for letting me know. I've built 6.1.22 from upstream and it
> > doesn't seem to crash.
>
> That's awesome :-) Let's hope it stays that way now ;-)
>
> You may have seen it on IRC already, but could you test a
> Debian 6.1.20-1 kernel with (only) those patches applied?
> These are the URLs:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.1.y&id=1c5abcb13491da8c049f20462189c12c753ba978
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.1.y&id=1e8525f37871741a52370627633962f8bdcab15a
>
> If you need help with that, feel free to ask :-)
>
> If we know that fixes the issue too, then we have the option of going for
> a 6.1.20-2 release with just those 2 patches (and what's already in -2 now).
>
Testing this now:
linux (6.1.20-1a~test) UNRELEASED; urgency=medium
* Testing patches ../0001-usb-ucsi-Fix-NULL-pointer-deref-in-
ucsi_connector_ch.patch ../0001-usb-ucsi_acpi-Increase-the-command-
completion-timeou.patch
-- Julien Cristau <jcristau@debian.org> Wed, 05 Apr 2023 11:09:30 +0000
and it doesn't seem to crash, as far as I can tell.
Cheers,
Julien
Reply to: