[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <43bbd12b-4754-92d1-4000-1ba928d2a8d4@amd.com>
Date: Fri, 28 Jul 2023 09:48:31 +0200
From: Christian König <christian.koenig@....com>
To: Asahi Lina <lina@...hilina.net>, alyssa@...enzweig.io,
Luben Tuikov <luben.tuikov@....com>,
David Airlie <airlied@...il.com>,
Daniel Vetter <daniel@...ll.ch>,
Sumit Semwal <sumit.semwal@...aro.org>
Cc: Faith Ekstrand <faith.ekstrand@...labora.com>,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org, asahi@...ts.linux.dev
Subject: Re: [PATCH 2/3] drm/scheduler: Fix UAF in
drm_sched_fence_get_timeline_name
Am 18.07.23 um 04:35 schrieb Asahi Lina:
> On 18/07/2023 00.55, Christian König wrote:
>> [SNIP]
>
> I give up. You are ignoring everything we say, and rejecting
> everything we suggest. We've already explained why drm_sched doesn't
> work for us. I'm tired of repeating the same explanation over and over
> again only to be ignored and told I'm wrong.
I'm not telling you that you are wrong in any way. What I'm pointing out
is that your solution won't work upstream and you need to take a step
back and think about why this won't work.
>
> I'll start working on a new, much simpler Rust-native scheduler based
> on the workqueue Rust abstractions which are in review.
Please note that when you are implementing a dma_fence interface you
also need my acknowledgement to get this upstream.
Additional to that Dave and Daniel might have objections to this as well.
Regards,
Christian.
>
> ~~ Lina
>
Powered by blists - more mailing lists