From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: Jeffrey Hugo <quic_jhugo@quicinc.com>
Cc: quic_carlv@quicinc.com, quic_pkanojiy@quicinc.com,
linux-arm-msm@vger.kernel.org, ogabbay@kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] accel/qaic: Use devm_drm_dev_alloc() instead of drm_dev_alloc()
Date: Mon, 4 Sep 2023 11:28:55 +0200 [thread overview]
Message-ID: <20230904092855.GC184247@linux.intel.com> (raw)
In-Reply-To: <20230901161236.8371-1-quic_jhugo@quicinc.com>
On Fri, Sep 01, 2023 at 10:12:36AM -0600, Jeffrey Hugo wrote:
> From: Pranjal Ramajor Asha Kanojiya <quic_pkanojiy@quicinc.com>
>
> Since drm_dev_alloc() is deprecated it is recommended to use
> devm_drm_dev_alloc() instead. Update the driver to start using
> devm_drm_dev_alloc().
>
> Signed-off-by: Pranjal Ramajor Asha Kanojiya <quic_pkanojiy@quicinc.com>
> Reviewed-by: Carl Vanderlip <quic_carlv@quicinc.com>
> Reviewed-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
> Signed-off-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
> + /*
> + * drm_dev_unregister() sets the driver data to NULL and
> + * drm_dev_register() does not update the driver data. During a SOC
> + * reset drm dev is unregistered and registered again leaving the
> + * driver data to NULL.
> + */
> + dev_set_drvdata(to_accel_kdev(qddev), drm->accel);
Yeah, explicitly nullified in drm_minor_unregister() with ' /* safety belt */
comment. I think in long term goal would be device reset not require
unregister/register.
> + drm_dev_get(drm);
> + drm_dev_unregister(drm);
That looks odd. I guess there is use-after-free problem if you just do
drm_dev_unregister(). Additional drm_dev_get() does not seems to be right
solution, but I'm not 100% sure, so ...
Reviewed-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
Regards
Stanislaw
next prev parent reply other threads:[~2023-09-04 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 16:12 [PATCH] accel/qaic: Use devm_drm_dev_alloc() instead of drm_dev_alloc() Jeffrey Hugo
2023-09-04 9:28 ` Stanislaw Gruszka [this message]
2023-09-15 15:36 ` Jeffrey Hugo
2023-09-15 15:37 ` Jeffrey Hugo
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=20230904092855.GC184247@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=ogabbay@kernel.org \
--cc=quic_carlv@quicinc.com \
--cc=quic_jhugo@quicinc.com \
--cc=quic_pkanojiy@quicinc.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