mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Peng Hao <penghao@dingdao.com>,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	airlied@gmail.com, daniel@ffwll.ch
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] gpu/drm/drm_framebuffer.c: Use Macro instead of actual number.
Date: Thu, 2 Nov 2023 14:27:09 +0100	[thread overview]
Message-ID: <40323b1b-b2de-45b2-88f2-d6b440e10f76@suse.de> (raw)
In-Reply-To: <20231102022946.115603-1-penghao@dingdao.com>


[-- Attachment #1.1: Type: text/plain, Size: 1831 bytes --]

Hi

Am 02.11.23 um 03:29 schrieb Peng Hao:
> Use Macro DRM_FORMAT_MAX_PLANES instead of 4, to improve modifiability.
> 
> Signed-off-by: Peng Hao <penghao@dingdao.com>
> ---
>   drivers/gpu/drm/drm_framebuffer.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/drm_framebuffer.c b/drivers/gpu/drm/drm_framebuffer.c
> index 2dd97473ca10..bf283dae9090 100644
> --- a/drivers/gpu/drm/drm_framebuffer.c
> +++ b/drivers/gpu/drm/drm_framebuffer.c
> @@ -254,7 +254,7 @@ static int framebuffer_check(struct drm_device *dev,
>   		}
>   	}
>   
> -	for (i = info->num_planes; i < 4; i++) {
> +	for (i = info->num_planes; i < DRM_FORMAT_MAX_PLANES; i++) {

This change makes the code more fragile. '4' is a fixed constant in the 
UAPI struct, while DRM_FORMAT_MAX_PLANES is an internal constant. I 
agree that both should reasonably have the same value. But (potentially) 
changing the value of DRM_FORMAT_MAX_PLANES will break these loops with 
a possible OOB access.

To make make this code more robust, it might be better to rewrite the 
tests like this

for (i = num_planes; i < ARRAY_SIZE(r->modifier); +i) {
	// the test for modifier[i]
}

if (r->flags & DRM_MODE_FB_MODIFIERS) {
  	for (i < ARRAY_SIZE(handles)) {
		// test for handles[i]
	}
  	for (i < ARRAY_SIZE(pitches)) {
		// test for pitches[i]
	}
  	for (i < ARRAY_SIZE(offsets)) {
		// test for offsets[i]
	}
}

Best regards
Thomas

>   		if (r->modifier[i]) {
>   			drm_dbg_kms(dev, "non-zero modifier for unused plane %d\n", i);
>   			return -EINVAL;

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

      parent reply	other threads:[~2023-11-02 13:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  2:29 Peng Hao
2023-11-02  6:32 ` Dmitry Baryshkov
2023-11-02 13:27 ` Thomas Zimmermann [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=40323b1b-b2de-45b2-88f2-d6b440e10f76@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=penghao@dingdao.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

all inboxes | Powered by JetHome®