linux-kernel - Re: [PATCH v2] drm/etnaviv: Fix flush sequence logic

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

Message-ID: <CAH9NwWfMCYKFF6Z+XiV9=4BANeyPk6bgNV_8FYM0cGwXuyDSxw@mail.gmail.com>
Date: Mon, 28 Jul 2025 00:28:42 +0200
From: Christian Gmeiner <christian.gmeiner@...il.com>
To: Tomeu Vizoso <tomeu@...euvizoso.net>
Cc: Lucas Stach <l.stach@...gutronix.de>, linux-kernel@...r.kernel.org, 
	Russell King <linux+etnaviv@...linux.org.uk>, David Airlie <airlied@...il.com>, 
	Simona Vetter <simona@...ll.ch>, Philipp Zabel <p.zabel@...gutronix.de>, 
	Guido Günther <agx@...xcpu.org>, 
	etnaviv@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org
Subject: Re: [PATCH v2] drm/etnaviv: Fix flush sequence logic

Hi Lucas,

> > > We should be comparing the last submitted sequence number with that of
> > > the address space we may be switching to.
> > >
> > This isn't the relevant change here though: if we switch the address
> > space, the comparison is moot, as we do a full flush on AS switch
> > anyway. The relevant change is that with the old code we would record
> > the flush sequence of the AS we switch away from as the current flush
> > sequence, so we might miss a necessary flush on the next submission if
> > that one doesn't require a AS switch, but would only flush based on
> > sequence mismatch.
>
> Ah, you are right.
>
> > Mind if I rewrite the commit message along those lines while applying?
>

Now that v6.16 has been tagged, I was wondering why this patch didn’t make
it into this release. From the timeline, it seemed like there was
enough time for it
to be included, so I’m just trying to understand if it was overlooked
or deferred
for a reason.

I also haven’t seen any recent activity at
https://git.pengutronix.de/cgit/lst/linux/, which
made me unsure about the current status of patch queue handling.

-- 
Thanks
--
Christian Gmeiner, MSc

https://christian-gmeiner.info/privacypolicy