From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Simon Ser <contact@emersion.fr>
Cc: Daniel Stone <daniels@collabora.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: pre-fill getfb2 modifier array with INVALID
Date: Thu, 11 Nov 2021 14:50:21 +0200 [thread overview]
Message-ID: <YY0RjSE7mI4kkKNJ@intel.com> (raw)
In-Reply-To: <20211111101049.269349-1-contact@emersion.fr>
On Thu, Nov 11, 2021 at 10:10:54AM +0000, Simon Ser wrote:
> User-space shouldn't look up the modifier array when the modifier
> flag is missing, but at the moment no docs make this clear (working
> on it). Right now the modifier array is pre-filled with zeroes, aka.
> LINEAR. Instead, pre-fill with INVALID to avoid footguns.
>
> This is a uAPI change, but OTOH any user-space which looks up the
> modifier array without checking the flag is broken already, so
> should be fine.
>
> Signed-off-by: Simon Ser <contact@emersion.fr>
> Cc: Daniel Vetter <daniel@ffwll.ch>
> Cc: Pekka Paalanen <ppaalanen@gmail.com>
> Cc: Daniel Stone <daniels@collabora.com>
Isn't this going to break the test where we pass the get
getfb2 result back into addfb2?
> ---
> 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 07f5abc875e9..f7041c0a0407 100644
> --- a/drivers/gpu/drm/drm_framebuffer.c
> +++ b/drivers/gpu/drm/drm_framebuffer.c
> @@ -601,7 +601,7 @@ int drm_mode_getfb2_ioctl(struct drm_device *dev,
> r->handles[i] = 0;
> r->pitches[i] = 0;
> r->offsets[i] = 0;
> - r->modifier[i] = 0;
> + r->modifier[i] = DRM_FORMAT_MOD_INVALID;
> }
>
> for (i = 0; i < fb->format->num_planes; i++) {
> --
> 2.33.1
>
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2021-11-11 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 10:10 [PATCH] drm: pre-fill getfb2 modifier array with INVALID Simon Ser
2021-11-11 11:08 ` Pekka Paalanen
2021-11-11 11:49 ` Daniel Stone
2021-11-11 12:50 ` Ville Syrjälä [this message]
2021-11-15 9:18 ` Simon Ser
2021-11-15 15:22 ` Ville Syrjälä
2021-11-15 15:26 ` Simon Ser
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=YY0RjSE7mI4kkKNJ@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=contact@emersion.fr \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.