Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1306995 > unrolled thread

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

Back to article view | Back to linux.kernel

Contents

  linux-next: build failure after merge of the aio tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-01-12 06:50 +0100
    Re: linux-next: build failure after merge of the aio tree Benjamin LaHaise <bcrl@kvack.org> - 2016-01-12 17:40 +0100
    Re: linux-next: build failure after merge of the aio tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-01-15 03:30 +0100
    Re: linux-next: build failure after merge of the aio tree Christoph Hellwig <hch@infradead.org> - 2016-01-15 08:40 +0100
      Re: linux-next: build failure after merge of the aio tree Christoph Hellwig <hch@infradead.org> - 2016-01-15 10:30 +0100
      Re: linux-next: build failure after merge of the aio tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-01-15 10:30 +0100

#1306995 — linux-next: build failure after merge of the aio tree

Hi Benjamin,

After merging the aio tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

fs/built-in.o: In function `aio_thread_op_foo_at':
file.c:(.text+0x43808): undefined reference to `__get_user_bad'
file.c:(.text+0x43838): undefined reference to `__get_user_bad'

Caused by commit

  150a0b4905f1 ("aio: add support for async openat()")

I have used the aio tree from next-20160111 for today.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[toc] | [next] | [standalone]

#1307615

On Tue, Jan 12, 2016 at 04:40:34PM +1100, Stephen Rothwell wrote:
> Hi Benjamin,
> 
> After merging the aio tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> fs/built-in.o: In function `aio_thread_op_foo_at':
> file.c:(.text+0x43808): undefined reference to `__get_user_bad'
> file.c:(.text+0x43838): undefined reference to `__get_user_bad'

This is very strange.  It seems to imply that __get_user() doesn't 
handle 64 bit values, which is completely broken behaviour on the 
architecture's part if true.  Can any ARM folks comment on the right 
fix here?

		-ben

> Caused by commit
> 
>   150a0b4905f1 ("aio: add support for async openat()")
> 
> I have used the aio tree from next-20160111 for today.
> 
> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au

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

[toc] | [prev] | [next] | [standalone]

#1309823

Hi Benjamin,

On Tue, 12 Jan 2016 16:40:34 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the aio tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> fs/built-in.o: In function `aio_thread_op_foo_at':
> file.c:(.text+0x43808): undefined reference to `__get_user_bad'
> file.c:(.text+0x43838): undefined reference to `__get_user_bad'
> 
> Caused by commit
> 
>   150a0b4905f1 ("aio: add support for async openat()")
> 
> I have used the aio tree from next-20160111 for today.

I am still getting this error.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[toc] | [prev] | [next] | [standalone]

#1309928

On Tue, Jan 12, 2016 at 04:40:34PM +1100, Stephen Rothwell wrote:
> Hi Benjamin,
> 
> After merging the aio tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> fs/built-in.o: In function `aio_thread_op_foo_at':
> file.c:(.text+0x43808): undefined reference to `__get_user_bad'
> file.c:(.text+0x43838): undefined reference to `__get_user_bad'
> 
> Caused by commit
> 
>   150a0b4905f1 ("aio: add support for async openat()")

How did that code end up in linux-next anyway?

[toc] | [prev] | [next] | [standalone]

#1309985

On Fri, Jan 15, 2016 at 08:23:16PM +1100, Stephen Rothwell wrote:
> Via the aio tree (git://git.kvack.org/~bcrl/aio-next.git#master) added
> in July 2013 at Ben's request.  The code was added to the aio tree in
> Jan 12 (my time), but has never been in a published linux-next tree due
> to the above build problem (I back out to the previous days version of
> the aio tree).

Well, it's code Ben posted a few days ago, which to say it mildly is
rather controversial.  It's cetainly not 4.5 material.

> 
> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au
---end quoted text---

[toc] | [prev] | [next] | [standalone]

#1309988

Hi Christoph,

On Thu, 14 Jan 2016 23:39:44 -0800 Christoph Hellwig <hch@infradead.org> wrote:
>
> On Tue, Jan 12, 2016 at 04:40:34PM +1100, Stephen Rothwell wrote:
> > Hi Benjamin,
> > 
> > After merging the aio tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> > 
> > fs/built-in.o: In function `aio_thread_op_foo_at':
> > file.c:(.text+0x43808): undefined reference to `__get_user_bad'
> > file.c:(.text+0x43838): undefined reference to `__get_user_bad'
> > 
> > Caused by commit
> > 
> >   150a0b4905f1 ("aio: add support for async openat()")  
> 
> How did that code end up in linux-next anyway?

Via the aio tree (git://git.kvack.org/~bcrl/aio-next.git#master) added
in July 2013 at Ben's request.  The code was added to the aio tree in
Jan 12 (my time), but has never been in a published linux-next tree due
to the above build problem (I back out to the previous days version of
the aio tree).

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web