linux-kernel - Re: [PATCH 2/2] drm/atomic: clear new_state pointers at hw

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJs_Fx6ErP9ap=veqJSrN-coKm_VV78wxqYLj_QF+-Gutk5AZA@mail.gmail.com>
Date:   Fri, 1 Nov 2019 12:44:04 -0700
From:   Rob Clark <robdclark@...omium.org>
To:     Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>
Cc:     Rob Clark <robdclark@...il.com>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        Sean Paul <seanpaul@...omium.org>,
        Maxime Ripard <mripard@...nel.org>,
        Sean Paul <sean@...rly.run>, David Airlie <airlied@...ux.ie>,
        Daniel Vetter <daniel@...ll.ch>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] drm/atomic: clear new_state pointers at hw_done

On Fri, Nov 1, 2019 at 11:33 AM Maarten Lankhorst
<maarten.lankhorst@...ux.intel.com> wrote:
>
> Op 01-11-2019 om 19:07 schreef Rob Clark:
> > From: Rob Clark <robdclark@...omium.org>
> >
> > The new state should not be accessed after this point.  Clear the
> > pointers to make that explicit.
> >
> > This makes the error corrected in the previous patch more obvious.
> >
> > Signed-off-by: Rob Clark <robdclark@...omium.org>
>
> Would be nice if you could cc intel-gfx@...ts.freedesktop.org next time, so I know our CI infrastructure is happy;
>
> It wouldn't surprise me if it catches 1 or 2 abuses in i915.
>
> Otherwise Reviewed-by: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>
>
> Perhaps you could mail this to version to intel-gfx-trybot@...ts.freedesktop.org using git-send-email so we at least get i915 results?

ok, I sent both patches to trybot, hopefully it tries them together,
as this patch without the self-refresh fix will definitely fall over

BR,
-R