Re: linux-next: build failure after merge of the aio tree

From	Benjamin LaHaise <bcrl@kvack.org>
Newsgroups	linux.kernel
Subject	Re: linux-next: build failure after merge of the aio tree
Date	2016-02-04 14:50 +0100
Message-ID	<qYssj-RV-45@gated-at.bofh.it> (permalink)
References	(1 earlier) <qQa9d-3tC-25@gated-at.bofh.it> <qVolc-57c-1@gated-at.bofh.it> <qWfze-2gW-49@gated-at.bofh.it> <qWg2e-2L2-5@gated-at.bofh.it> <qYhQd-2mU-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Thu, Feb 04, 2016 at 01:19:59PM +1100, Stephen Rothwell wrote:
> Hi Benjamin,
> 
> On Fri, 29 Jan 2016 13:03:39 +0100 Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> >
> > On Fri, Jan 29, 2016 at 12:30 PM, Russell King - ARM Linux
> > <linux@arm.linux.org.uk> wrote:
> > >> Background: new aio code is adding __get_user() calls referencing 64
> > >> bit quantities (__u64 and __s64).  
> > >
> > > There's lots more architectures which do not support 64-bit get_user()
> > > _or_ __get_user(): avr32, blackfin, metag for example, and m68k which
> > > has this interesting thing "/* case 8: disabled because gcc-4.1 has a
> > > broken typeof \" in its *get_user() implementation.  
> > 
> > And if you enable it again, you get lots of "warning: cast to pointer from
> > integer of different size", like you mentioned.
> 
> Any thoughts?  I am still using the version of tha aio tree from
> next-20160111.

I am still convinced that this is an architecture issue.  Given that 64 bit 
values work in the *get_user implementations on other architectures, I see 
no reason there should need to be a workaround for this in common code.

		-ben

> -- 
> Cheers,
> Stephen Rothwell

-- 
"Thought is the essence of where you are now."

Thread

Re: linux-next: build failure after merge of the aio tree Russell King - ARM Linux <linux@arm.linux.org.uk> - 2016-01-29 12:40 +0100
  Re: linux-next: build failure after merge of the aio tree Geert Uytterhoeven <geert@linux-m68k.org> - 2016-01-29 13:10 +0100
    Re: linux-next: build failure after merge of the aio tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-02-04 03:30 +0100
      Re: linux-next: build failure after merge of the aio tree Benjamin LaHaise <bcrl@kvack.org> - 2016-02-04 14:50 +0100
        Re: linux-next: build failure after merge of the aio tree Russell King - ARM Linux <linux@arm.linux.org.uk> - 2016-02-04 15:00 +0100
          Re: linux-next: build failure after merge of the aio tree Benjamin LaHaise <bcrl@kvack.org> - 2016-02-04 15:10 +0100
            Re: linux-next: build failure after merge of the aio tree Russell King - ARM Linux <linux@arm.linux.org.uk> - 2016-02-04 15:20 +0100
              Re: linux-next: build failure after merge of the aio tree Russell King - ARM Linux <linux@arm.linux.org.uk> - 2016-02-04 15:40 +0100
                Re: linux-next: build failure after merge of the aio tree Benjamin LaHaise <bcrl@kvack.org> - 2016-02-04 17:10 +0100
                Re: linux-next: build failure after merge of the aio tree Russell King - ARM Linux <linux@arm.linux.org.uk> - 2016-02-04 17:20 +0100
                Re: linux-next: build failure after merge of the aio tree Benjamin LaHaise <bcrl@kvack.org> - 2016-02-04 17:30 +0100
                Re: linux-next: build failure after merge of the aio tree Benjamin LaHaise <bcrl@kvack.org> - 2016-02-04 17:50 +0100
                Re: linux-next: build failure after merge of the aio tree Benjamin LaHaise <bcrl@kvack.org> - 2016-02-04 19:50 +0100
              Re: linux-next: build failure after merge of the aio tree Benjamin LaHaise <bcrl@kvack.org> - 2016-02-04 15:40 +0100

csiph-web