From: Danilo Krummrich <dakr@redhat.com>
To: Maxime Ripard <maxime@cerno.tech>
Cc: airlied@linux.ie, dri-devel@lists.freedesktop.org,
emma@anholt.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] drm/vc4: use drm managed resources
Date: Thu, 14 Jul 2022 16:27:40 +0200 [thread overview]
Message-ID: <dda65c68-cea4-4323-b061-8fc2048bd604@redhat.com> (raw)
In-Reply-To: <20220713091049.qy4t3j3hh5jgtqum@houat>
Hi Maxime,
On 7/13/22 11:10, Maxime Ripard wrote:
> Hi Danilo,
>
> On Wed, Jul 13, 2022 at 10:54:57AM +0200, Danilo Krummrich wrote:
>> This patch series converts DRM modeset object allocations from devm_*()
>> to drmm_*() memory allocators, or their corresponding convenience
>> wrappers, respectively, in order to tie the release action to the
>> underlaying struct drm_device.
>>
>> This can prevent potential use-after free issues on driver unload or
>> EPROBE_DEFERRED backoff.
>
> Yeah, the driver had a lot of this kind of issues.
>
> As it turns out, at the moment you sent it, I was applying a larger
> series (hopefully) addressing all of them:
> https://lore.kernel.org/all/20220711173939.1132294-1-maxime@cerno.tech/
Ah, great! That's covering even more than the series I sent.
>
> Maxime
- Danilo
prev parent reply other threads:[~2022-07-14 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 8:54 Danilo Krummrich
2022-07-13 8:54 ` [PATCH 1/3] drm/vc4: plane: " Danilo Krummrich
2022-07-13 8:54 ` [PATCH 2/3] drm/vc4: crtc: " Danilo Krummrich
2022-07-13 8:55 ` [PATCH 3/3] drm/vc4: encoder: " Danilo Krummrich
2022-07-13 9:10 ` [PATCH 0/3] drm/vc4: " Maxime Ripard
2022-07-14 14:27 ` Danilo Krummrich [this message]
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=dda65c68-cea4-4323-b061-8fc2048bd604@redhat.com \
--to=dakr@redhat.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=emma@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime@cerno.tech \
/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
all inboxes | Powered by JetHome®