From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 5/7] drm: plane: Check crtc coodrinates against integer overflows in setplane ioctl
Date: Fri, 11 Nov 2011 19:11:39 +0200 [thread overview]
Message-ID: <20111111171139.GD3477@intel.com> (raw)
In-Reply-To: <20111111090146.53157706@jbarnes-desktop>
On Fri, Nov 11, 2011 at 09:01:46AM -0800, Jesse Barnes wrote:
> On Fri, 11 Nov 2011 18:04:05 +0200
> ville.syrjala@linux.intel.com wrote:
>
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Help drivers a little by guaranteeing that crtc_x+crtc_w and
> > crtc_y+crtc_h don't overflow.
> >
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/drm_crtc.c | 12 ++++++++++++
> > 1 files changed, 12 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c
> > index 098cc50..2410a9a 100644
> > --- a/drivers/gpu/drm/drm_crtc.c
> > +++ b/drivers/gpu/drm/drm_crtc.c
> > @@ -1725,6 +1725,18 @@ int drm_mode_setplane(struct drm_device *dev, void *data,
> > goto out;
> > }
> >
> > + /* Give drivers some help against integer overflows */
> > + if (plane_req->crtc_w > INT_MAX ||
> > + plane_req->crtc_x > INT_MAX - (int32_t) plane_req->crtc_w ||
> > + plane_req->crtc_h > INT_MAX ||
> > + plane_req->crtc_y > INT_MAX - (int32_t) plane_req->crtc_h) {
> > + DRM_DEBUG_KMS("Invalid CRTC coordinates %ux%u+%d+%d\n",
> > + plane_req->crtc_w, plane_req->crtc_h,
> > + plane_req->crtc_x, plane_req->crtc_y);
> > + ret = -EINVAL;
> > + goto out;
> > + }
> > +
> > ret = plane->funcs->update_plane(plane, crtc, fb,
> > plane_req->crtc_x, plane_req->crtc_y,
> > plane_req->crtc_w, plane_req->crtc_h,
>
> Not sure this helps much in practice, since the drivers will have to
> validate the target CRTC rect against the actual pipe dimensions anyway.
My master plan is that drivers would just stick these into a drm_region
(introduced in my other patchset) and clip that to the pipe dimensions.
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2011-11-11 17:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 16:04 drm plane fixes and additional checks ville.syrjala
2011-11-11 16:04 ` [PATCH 1/7] drm: Zero initialize drm_mode_fb_cmd2 in legacy addfb ioctl handler ville.syrjala
2011-11-11 16:55 ` Jesse Barnes
2011-11-11 16:04 ` [PATCH 2/7] drm: plane: Fix size of formats memcpy() ville.syrjala
2011-11-11 16:22 ` Jesse Barnes
2011-11-11 16:04 ` [PATCH 3/7] drm: plane: Clear plane.crtc and plane.fb after disable_plane() ville.syrjala
2011-11-11 16:56 ` Jesse Barnes
2011-11-11 16:04 ` [PATCH 4/7] drm: plane: Check source coordinates ville.syrjala
2011-11-11 16:24 ` Jesse Barnes
2011-11-11 17:18 ` Ville Syrjälä
2011-11-11 17:20 ` Jesse Barnes
2011-11-11 16:04 ` [PATCH 5/7] drm: plane: Check crtc coodrinates against integer overflows in setplane ioctl ville.syrjala
2011-11-11 17:01 ` Jesse Barnes
2011-11-11 17:11 ` Ville Syrjälä [this message]
2011-11-11 17:21 ` Jesse Barnes
2011-11-11 16:04 ` [PATCH 6/7] drm: plane: Make 'formats' parameter to drm_plane_init() const ville.syrjala
2011-11-11 16:25 ` Jesse Barnes
2011-11-11 16:04 ` [PATCH 7/7] drm: plane: Check that the fb pixel format is supported by the plane ville.syrjala
2011-11-11 16:25 ` Jesse Barnes
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=20111111171139.GD3477@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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.