From: "Jason-JH Lin (林睿祥)" <Jason-JH.Lin@mediatek.com>
To: "daniel@ffwll.ch" <daniel@ffwll.ch>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"michel@daenzer.net" <michel@daenzer.net>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"mikita.lipski@amd.com" <mikita.lipski@amd.com>,
"dmitry.baryshkov@linaro.org" <dmitry.baryshkov@linaro.org>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"maxime@cerno.tech" <maxime@cerno.tech>,
"daniel.vetter@intel.com" <daniel.vetter@intel.com>,
"nicholas.kazlauskas@amd.com" <nicholas.kazlauskas@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"quic_abhinavk@quicinc.com" <quic_abhinavk@quicinc.com>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"manasi.d.navare@intel.com" <manasi.d.navare@intel.com>,
"lucas.demarchi@intel.com" <lucas.demarchi@intel.com>,
"sean@poorly.run" <sean@poorly.run>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"dmitry.osipenko@collabora.com" <dmitry.osipenko@collabora.com>,
"fshao@chromium.org" <fshao@chromium.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"jani.nikula@intel.com" <jani.nikula@intel.com>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"freedreno@lists.freedesktop.org"
<freedreno@lists.freedesktop.org>
Subject: Re: [PATCH] drm/atomic-helpers: remove legacy_cursor_update hacks
Date: Wed, 31 Jan 2024 05:17:08 +0000 [thread overview]
Message-ID: <1349365de499bae53a8c868738c7270fc16813d5.camel@mediatek.com> (raw)
In-Reply-To: <ZbKlsTEvGPiGtzS3@phenom.ffwll.local>
On Thu, 2024-01-25 at 19:17 +0100, Daniel Vetter wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> On Tue, Jan 23, 2024 at 06:09:05AM +0000, Jason-JH Lin (林睿祥) wrote:
> > Hi Maxime, Daniel,
> >
> > We encountered similar issue with mediatek SoCs.
> >
> > We have found that in drm_atomic_helper_commit_rpm(), when
> disabling
> > the cursor plane, the old_state->legacy_cursor_update in
> > drm_atomic_wait_for_vblank() is set to true.
> > As the result, we are not actually waiting for a vlbank to wait for
> our
> > hardware to close the cursor plane. Subsequently, the execution
> > proceeds to drm_atomic_helper_cleanup_planes() to free the cursor
> > buffer. This can lead to use-after-free issues with our hardware.
> >
> > Could you please apply this patch to fix our problem?
> > Or are there any considerations for not applying this patch?
>
> Mostly it needs someone to collect a pile of acks/tested-by and then
> land
> it.
>
Got it. I would add tested-by tag for mediatek SoC.
> I'd be _very_ happy if someone else can take care of that ...
>
> There's also the potential issue that it might slow down some of the
> legacy X11 use-cases that really needed a non-blocking cursor, but I
> think
> all the drivers where this matters have switched over to the async
> plane
> update stuff meanwhile. So hopefully that's good.
>
I think all the drivers should have switched to async plane update.
Can we add the checking condition to see if atomic_async_update/check
function are implemented?
Regards,
Jason-JH.Lin
> Cheers, Sima
> >
> > Regards,
> > Jason-JH.Lin
> >
> > On Tue, 2023-03-07 at 15:56 +0100, Maxime Ripard wrote:
> > > Hi,
> > >
> > > On Thu, Feb 16, 2023 at 12:12:13PM +0100, Daniel Vetter wrote:
> > > > The stuff never really worked, and leads to lots of fun because
> it
> > > > out-of-order frees atomic states. Which upsets KASAN, among
> other
> > > > things.
> > > >
> > > > For async updates we now have a more solid solution with the
> > > > ->atomic_async_check and ->atomic_async_commit hooks. Support
> for
> > > > that
> > > > for msm and vc4 landed. nouveau and i915 have their own commit
> > > > routines, doing something similar.
> > > >
> > > > For everyone else it's probably better to remove the use-after-
> free
> > > > bug, and encourage folks to use the async support instead. The
> > > > affected drivers which register a legacy cursor plane and don't
> > > > either
> > > > use the new async stuff or their own commit routine are:
> amdgpu,
> > > > atmel, mediatek, qxl, rockchip, sti, sun4i, tegra, virtio, and
> > > > vmwgfx.
> > > >
> > > > Inspired by an amdgpu bug report.
> > >
> > > Thanks for submitting that patch. It's been in the downstream RPi
> > > tree
> > > for a while, so I'd really like it to be merged eventually :)
> > >
> > > Acked-by: Maxime Ripard <maxime@cerno.tech>
> > >
> > > Maxime
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-31 5:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 11:12 [PATCH] drm/atomic-helpers: remove legacy_cursor_update hacks Daniel Vetter
2023-02-22 23:14 ` Rob Clark
2023-02-22 23:21 ` Rob Clark
2023-03-07 14:56 ` Maxime Ripard
2024-01-23 6:09 ` Jason-JH Lin (林睿祥)
2024-01-25 18:17 ` Daniel Vetter
2024-01-28 9:24 ` Maxime Ripard
2024-01-31 5:27 ` Jason-JH Lin (林睿祥)
2024-01-31 10:57 ` mripard
2024-01-31 5:17 ` Jason-JH Lin (林睿祥) [this message]
2024-01-31 9:11 ` Daniel Vetter
2024-01-31 10:26 ` Dmitry Baryshkov
2024-01-31 11:28 ` Daniel Vetter
2025-01-13 8:28 ` maxime
2025-01-13 9:01 ` Dmitry Baryshkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1349365de499bae53a8c868738c7270fc16813d5.camel@mediatek.com \
--to=jason-jh.lin@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dmitry.osipenko@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=fshao@chromium.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lucas.demarchi@intel.com \
--cc=manasi.d.navare@intel.com \
--cc=matthias.bgg@gmail.com \
--cc=maxime@cerno.tech \
--cc=michel@daenzer.net \
--cc=mikita.lipski@amd.com \
--cc=nicholas.kazlauskas@amd.com \
--cc=quic_abhinavk@quicinc.com \
--cc=sean@poorly.run \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox