From: Yannick FERTRE <yannick.fertre@foss.st.com>
To: Katya Orlova <e.orlova@ispras.ru>
Cc: Philippe Cornu <philippe.cornu@foss.st.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
<dri-devel@lists.freedesktop.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <lvc-project@linuxtesting.org>,
Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
Subject: Re: TR: [PATCH v4] drm/stm: Avoid use-after-free issues with crtc and plane
Date: Fri, 21 Jun 2024 15:32:53 +0200 [thread overview]
Message-ID: <902e6037-9ba9-41ab-bfd0-a25fe2c26bce@foss.st.com> (raw)
In-Reply-To: <ef635048bc7b4521be09ca06c66b57a5@foss.st.com>
Hi Katya,
thanks for the patch.
Tested-by: Yannick Fertre <yannick.fertre@foss.st.com>
BR
Le 19/03/2024 à 14:47, Philippe CORNU - foss a écrit :
> zut, déjà un acked-by de RGA...
> tu confirmes que je prends?
> Philippe
> ________________________________________
> De : Raphael GALLAIS-POU - foss
> Envoyé : lundi 26 février 2024 14:50
> À : Katya Orlova
> Cc : Yannick FERTRE - foss; Philippe CORNU - foss; David Airlie; Daniel Vetter; Maxime Coquelin; Alexandre TORGUE - foss; Philipp Zabel; dri-devel@lists.freedesktop.org; linux-stm32@st-md-mailman.stormreply.com; linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org; lvc-project@linuxtesting.org
> Objet : Re: [PATCH v4] drm/stm: Avoid use-after-free issues with crtc and plane
>
> On 2/16/24 13:50, Katya Orlova wrote:
>> ltdc_load() calls functions drm_crtc_init_with_planes(),
>> drm_universal_plane_init() and drm_encoder_init(). These functions
>> should not be called with parameters allocated with devm_kzalloc()
>> to avoid use-after-free issues [1].
>>
>> Use allocations managed by the DRM framework.
>>
>> Found by Linux Verification Center (linuxtesting.org).
>>
>> [1]
>> https://lore.kernel.org/lkml/u366i76e3qhh3ra5oxrtngjtm2u5lterkekcz6y2jkndhuxzli@diujon4h7qwb/
>>
>> Signed-off-by: Katya Orlova <e.orlova@ispras.ru>
> Hi Katya,
>
>
> Thanks for this submission.
>
> Acked-by: Raphaël Gallais-Pou <raphael.gallais-pou@foss.st.com>
>
>
> Regards,
> Raphaël
>
next prev parent reply other threads:[~2024-06-21 13:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 10:29 [PATCH] drm/stm: Avoid use-after-free issues with crtc and plane Katya Orlova
2023-10-23 8:19 ` Raphael Gallais-Pou
2023-11-24 10:04 ` [PATCH v2] " Katya Orlova
2024-01-05 9:21 ` Raphael Gallais-Pou
2024-01-22 11:11 ` [PATCH v3] " Katya Orlova
2024-02-16 12:50 ` [PATCH v4] " Katya Orlova
2024-02-26 13:50 ` Raphael Gallais-Pou
[not found] ` <ef635048bc7b4521be09ca06c66b57a5@foss.st.com>
2024-06-21 13:32 ` Yannick FERTRE [this message]
2024-07-15 9:12 ` Raphael Gallais-Pou
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=902e6037-9ba9-41ab-bfd0-a25fe2c26bce@foss.st.com \
--to=yannick.fertre@foss.st.com \
--cc=airlied@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=e.orlova@ispras.ru \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lvc-project@linuxtesting.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=philippe.cornu@foss.st.com \
--cc=raphael.gallais-pou@foss.st.com \
/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;
as well as URLs for NNTP newsgroup(s).