[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100512124244.20365b3c.randy.dunlap@oracle.com>
Date: Wed, 12 May 2010 12:42:44 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Jeff Moyer <jmoyer@...hat.com>, Jack Steiner <steiner@....com>
Cc: linux-kernel@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: mmotm 2010-05-11-18-20 uploaded (aio build; add numa)
On Wed, 12 May 2010 13:07:58 -0400 Jeff Moyer wrote:
> Randy Dunlap <randy.dunlap@...cle.com> writes:
>
> > On Tue, 11 May 2010 18:21:22 -0700 akpm@...ux-foundation.org wrote:
> >
> >> The mm-of-the-moment snapshot 2010-05-11-18-20 has been uploaded to
> >>
> >> http://userweb.kernel.org/~akpm/mmotm/
> >>
> >> and will soon be available at
> >>
> >> git://zen-kernel.org/kernel/mmotm.git
> >
> >
> > aio-fix-the-compat-vectored-operations.patch:
> >
> > (1) when CONFIG_AIO is not enabled, there are hundreds of this warning:
> >
> > include/linux/aio.h:226: warning: no return statement in function returning non-void
> >
> >
> > (2) when CONFIG_AIO=y, CONFIG_IA32_EMULATION=n, CONFIG_COMPAT=n:
> >
> > fs/aio.c:1393: error: implicit declaration of function 'compat_rw_copy_check_uvector'
>
> Sorry about that. I'll fix it up, but probably can't get to it until
> Monday. Hopefully that's an ok timeframe.
Andrew's patch works_for_me. (Ack)
During the build, I got another (unrelated) build error:
kernel/built-in.o: In function `copy_process':
fork.c:(.text+0x162b6): undefined reference to `__node_random'
fork.c:(.text+0x162cd): undefined reference to `__node_random'
kernel/fork.c needs to #include <linux/nodemask.h>
[builds...]
But that is not enough. The config file has CONFIG_CPUSETS=y
and CONFIG_NUMA=n, so __node_random() is not being built at all.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists