From: Liviu Dudau <liviu.dudau@arm.com>
To: Steven Price <steven.price@arm.com>
Cc: David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH] drm/plane: Move range check for format_count earlier
Date: Thu, 28 Apr 2022 16:00:42 +0100 [thread overview]
Message-ID: <YmqsGhEzaZsdZs3u@e110455-lin.cambridge.arm.com> (raw)
In-Reply-To: <0b3136fa-8fd1-5496-812e-c03e430da84a@arm.com>
On Thu, Apr 28, 2022 at 12:57:52PM +0100, Steven Price wrote:
> On 03/12/2021 13:08, Liviu Dudau wrote:
> > On Fri, Dec 03, 2021 at 10:28:15AM +0000, Steven Price wrote:
> >> While the check for format_count > 64 in __drm_universal_plane_init()
> >> shouldn't be hit (it's a WARN_ON), in its current position it will then
> >> leak the plane->format_types array and fail to call
> >> drm_mode_object_unregister() leaking the modeset identifier. Move it to
> >> the start of the function to avoid allocating those resources in the
> >> first place.
> >>
> >> Signed-off-by: Steven Price <steven.price@arm.com>
> >
> > Well spotted!
> >
> > Reviewed-by: Liviu Dudau <liviu.dudau@arm.com>
> >
> > I'm going to wait to see if anyone else has any comments before I'll merge this into
> > drm-misc-fixes (or should it be drm-misc-next-fixes?)
>
> Gentle ping! I think we've probably waited long enough. Are you going to
> merge this or would you like me to?
Apologies for dropping this! I will push this one today.
Best regards,
Liviu
>
> Thanks,
>
> Steve
>
> > Best regards,
> > Liviu
> >
> >> ---
> >> drivers/gpu/drm/drm_plane.c | 14 +++++++-------
> >> 1 file changed, 7 insertions(+), 7 deletions(-)
> >>
> >> diff --git a/drivers/gpu/drm/drm_plane.c b/drivers/gpu/drm/drm_plane.c
> >> index 82afb854141b..fd0bf90fb4c2 100644
> >> --- a/drivers/gpu/drm/drm_plane.c
> >> +++ b/drivers/gpu/drm/drm_plane.c
> >> @@ -249,6 +249,13 @@ static int __drm_universal_plane_init(struct drm_device *dev,
> >> if (WARN_ON(config->num_total_plane >= 32))
> >> return -EINVAL;
> >>
> >> + /*
> >> + * First driver to need more than 64 formats needs to fix this. Each
> >> + * format is encoded as a bit and the current code only supports a u64.
> >> + */
> >> + if (WARN_ON(format_count > 64))
> >> + return -EINVAL;
> >> +
> >> WARN_ON(drm_drv_uses_atomic_modeset(dev) &&
> >> (!funcs->atomic_destroy_state ||
> >> !funcs->atomic_duplicate_state));
> >> @@ -270,13 +277,6 @@ static int __drm_universal_plane_init(struct drm_device *dev,
> >> return -ENOMEM;
> >> }
> >>
> >> - /*
> >> - * First driver to need more than 64 formats needs to fix this. Each
> >> - * format is encoded as a bit and the current code only supports a u64.
> >> - */
> >> - if (WARN_ON(format_count > 64))
> >> - return -EINVAL;
> >> -
> >> if (format_modifiers) {
> >> const uint64_t *temp_modifiers = format_modifiers;
> >>
> >> --
> >> 2.25.1
> >>
> >
>
--
====================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
¯\_(ツ)_/¯
prev parent reply other threads:[~2022-04-28 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 10:28 Steven Price
2021-12-03 13:08 ` Liviu Dudau
2022-04-28 11:57 ` Steven Price
2022-04-28 15:00 ` Liviu Dudau [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=YmqsGhEzaZsdZs3u@e110455-lin.cambridge.arm.com \
--to=liviu.dudau@arm.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steven.price@arm.com \
--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
all inboxes | Powered by JetHome®