Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Feedback-ID: i8771445c:Fastmail
Date:   Wed, 13 Jul 2022 11:10:49 +0200
From:   Maxime Ripard <maxime@cerno.tech>
To:     Danilo Krummrich <dakr@redhat.com>
Cc:     emma@anholt.net, daniel@ffwll.ch, airlied@linux.ie,
        dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] drm/vc4: use drm managed resources
Message-ID: <20220713091049.qy4t3j3hh5jgtqum@houat>
References: <20220713085500.1970589-1-dakr@redhat.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="y6sjhfw424vcozzy"
Content-Disposition: inline
In-Reply-To: <20220713085500.1970589-1-dakr@redhat.com>
Precedence: bulk


--y6sjhfw424vcozzy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.
>=20
> 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/

Maxime

--y6sjhfw424vcozzy
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCYs6MGQAKCRDj7w1vZxhR
xV4RAQDCppbyA6im9Xueg9td+P9gvsqPNJOcFq1JWDW0YbDcDAD/elvnok9QdFTd
xVLGTke67JLDU7YOna+ORGGc8891gw0=
=jDoO
-----END PGP SIGNATURE-----

--y6sjhfw424vcozzy--