From: Daniel Vetter <daniel@ffwll.ch>
To: Borislav Petkov <bp@alien8.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm, i915: Fix pointer size cast
Date: Mon, 21 Dec 2015 20:20:21 +0100 [thread overview]
Message-ID: <20151221192021.GN30437@phenom.ffwll.local> (raw)
In-Reply-To: <1450724039-23264-1-git-send-email-bp@alien8.de>
On Mon, Dec 21, 2015 at 07:53:59PM +0100, Borislav Petkov wrote:
> From: Borislav Petkov <bp@suse.de>
>
> gcc complains on 32-bit like this:
>
> drivers/gpu/drm/i915/intel_display.c: In function ‘intel_plane_obj_offset’:
> drivers/gpu/drm/i915/intel_display.c:2954:11: warning: cast to pointer from \
> integer of different size [-Wint-to-pointer-cast]
> offset = (unsigned char *)vma->node.start;
> ^
>
> because vma->node.start is u64 but a pointer on 32-bit is 4 bytes.
>
> Do the calculations with an unsigned long directly and save us the
> casts.
>
> Cc: Daniel Vetter <daniel.vetter@intel.com>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Cc: David Airlie <airlied@linux.ie>
> Cc: intel-gfx@lists.freedesktop.org
> Cc: dri-devel@lists.freedesktop.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Borislav Petkov <bp@suse.de>
This has been fixed already in
commit 44eb0cb9620c6a53ec8e7073262e2af8079b727f
Author: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Date: Fri Oct 30 13:26:15 2015 +0200
drm/i915: Avoid pointer arithmetic in calculating plane surface offset
Cheers,
Daniel
> ---
> drivers/gpu/drm/i915/intel_display.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 62211abe4922..640cb7c9b7f3 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -2941,7 +2941,7 @@ unsigned long intel_plane_obj_offset(struct intel_plane *intel_plane,
> {
> const struct i915_ggtt_view *view = &i915_ggtt_view_normal;
> struct i915_vma *vma;
> - unsigned char *offset;
> + unsigned long offset;
>
> if (intel_rotation_90_or_270(intel_plane->base.state->rotation))
> view = &i915_ggtt_view_rotated;
> @@ -2951,14 +2951,14 @@ unsigned long intel_plane_obj_offset(struct intel_plane *intel_plane,
> view->type))
> return -1;
>
> - offset = (unsigned char *)vma->node.start;
> + offset = vma->node.start;
>
> if (plane == 1) {
> offset += vma->ggtt_view.rotation_info.uv_start_page *
> PAGE_SIZE;
> }
>
> - return (unsigned long)offset;
> + return offset;
> }
>
> static void skl_detach_scaler(struct intel_crtc *intel_crtc, int id)
> --
> 2.3.5
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2015-12-21 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 18:53 [PATCH] drm, i915: Fix pointer size cast Borislav Petkov
2015-12-21 19:20 ` Daniel Vetter [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=20151221192021.GN30437@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=bp@alien8.de \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).