linux-kernel - Re: [git pull] drm for 5.20/6.0

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAPM=9txwzNZgUCJUTxww3hYmTnbrNH-2zdjxamxB4=yW9sFHxQ@mail.gmail.com>
Date:   Thu, 4 Aug 2022 15:52:25 +1000
From:   Dave Airlie <airlied@...il.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Rodrigo Siqueira <Rodrigo.Siqueira@....com>,
        Daniel Wheeler <daniel.wheeler@....com>,
        Harry Wentland <Harry.Wentland@....com>,
        Alex Deucher <alexander.deucher@....com>,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm for 5.20/6.0

On Thu, 4 Aug 2022 at 15:25, Dave Airlie <airlied@...il.com> wrote:
>
> On Thu, 4 Aug 2022 at 14:46, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
> >
> > On Wed, Aug 3, 2022 at 9:27 PM Linus Torvalds
> > <torvalds@...ux-foundation.org> wrote:
> > >
> > > I'll do a few more. It's close enough already that it should be just
> > > four more reboots to pinpoint exactly which commit breaks.
> >
> > commit 5d945cbcd4b16a29d6470a80dfb19738f9a4319f is the first bad commit.
> >
> > I think it's supposed to make no semantic changes, but it clearly does.
> >
> > What a pain to figure out what's wrong in there, and I assume it
> > doesn't revert cleanly either.
> >
> > Bringing in the guilty parties. See
> >
> >   https://lore.kernel.org/all/CAHk-=wj+yzauNXiEwHfCrkbdLSQkizdR1Q3YJLAqPo6AVq2_4Q@mail.gmail.com/
> >
> > for the beginning of this thread.
>
> I think I've tracked it down, looks like it would only affect GFX8
> cards, which might explain why you and I have seen it, and I haven't
> seen any other reports.
>
> pretty sure you have an rx580, and I just happen to have a fiji card
> in this machine right now.
>
> I'll retest on master and send you a fixup patch.

To close the loop

https://lore.kernel.org/all/20220804055036.691670-1-airlied@redhat.com/T/#u

Seems to fix it here.

Dave.