linux-kernel - Re: drivers/gpu/drm/i915/intel_display.c:2954:11: warning: cast to pointer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 9 Sep 2016 13:55:03 +0100
From:   Nick Warne <nick@...icks.net>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Daniel Vetter <daniel.vetter@...el.com>,
        linux-kernel@...r.kernel.org
Subject: Re: drivers/gpu/drm/i915/intel_display.c:2954:11: warning: cast to
 pointer

On Fri, 9 Sep 2016 13:55:45 +0200
Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:

> On Thu, Sep 08, 2016 at 04:59:53PM +0100, Nick Warne wrote:
> > On Thu, 8 Sep 2016 08:29:37 +0200
> > Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
> >   
> > > On Wed, Sep 07, 2016 at 05:38:52PM +0100, Nick Warne wrote:  
> > > > Hi Daniel,
> > > > 
> > > > kernel build 4.4.20 - I am still seeing this warning:
> > > > 
> > > > drivers/gpu/drm/i915/intel_display.c: In function
> > > > ‘intel_plane_obj_offset’:
> > > > drivers/gpu/drm/i915/intel_display.c:2969:11: warning: cast to
> > > > pointer from integer of different size [-Wint-to-pointer-cast]
> > > > offset = (unsigned char *)vma->node.start;
> > > > 
> > > > but according to here:
> > > > 
> > > > https://patchwork.kernel.org/patch/7897461/
> > > > 
> > > > this has been fixed up.  Any reason why it hasn't in the latest
> > > > 4.4.x longterm tree?    
> > > 
> > > What is the commit id that fixed this in Linus's tree?  
> > 
> > Took me a while to find it if this is it - a bit of a re-write in
> > the whole file I think:
> > 
> > https://github.com/torvalds/linux/commit/44eb0cb9620c6a53ec8e7073262e2af8079b727f  
> 
> Ick, messy.
> 
> Why not just use 4.7?  Why are you stuck at 4.4?

I only recently moved over to 4.4 from 3.18.x as it's longterm
support. I may try 4.7 over the weekend - or maybe even just use the
patchwork diff on my own local builds.

> And is this a real bug in 4.4 or just a build warning?

No, it's not a bug (that I have found or seen, anyway), just GCC
squinnying.

Thanks for your help, and sorry for the noise.

Nick
-- 
Gosh that takes me back... or is it forward?  That's the trouble with
time travel, you never can tell."
		-- Doctor Who "Androids of Tara"