[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090128163040.88b05b3d.akpm@linux-foundation.org>
Date: Wed, 28 Jan 2009 16:30:40 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Randy Dunlap <randy.dunlap@...cle.com>
Cc: linux-kernel@...r.kernel.org, Miao Xie <miaox@...fujitsu.com>,
Neil Horman <nhorman@...driver.com>,
Simon Horman <horms@...ge.net.au>,
Vivek Goyal <vgoyal@...hat.com>
Subject: Re: mmotm 2009-01-28-02-17 uploaded (i386 build errors: cpusets &
kexec)
On Wed, 28 Jan 2009 08:56:31 -0800
Randy Dunlap <randy.dunlap@...cle.com> wrote:
> akpm@...ux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2009-01-28-02-17 has been uploaded to
> >
> > http://userweb.kernel.org/~akpm/mmotm/
> >
> > and will soon be available at
> >
> > git://git.zen-sources.org/zen/mmotm.git
>
>
> 10 randconfigs on i386, 1 good build.
>
> The other 9 ended with either of these build errors:
>
> init/main.c:876: error: 'struct task_struct' has no member named 'mems_allowed'
> CONFIG_CPUSETS=n
Well that sucks a bit.
--- a/init/main.c~cpuset-fix-allocating-page-cache-slab-object-on-the-unallowed-node-when-memory-spread-is-set-fix
+++ a/init/main.c
@@ -873,7 +873,9 @@ static int __init kernel_init(void * unu
*/
init_pid_ns.child_reaper = current;
+#ifdef CONFIG_CPUSETS
current->mems_allowed = node_possible_map;
+#endif
cad_pid = task_pid(current);
_
>
> or
>
> kernel/printk.c:142: error: implicit declaration of function 'VMCOREINFO_SYMBOL'
> # CONFIG_KEXEC is not set
>
So does that.
--- a/kernel/printk.c~kexec-add-dmesg-log-symbols-to-proc-vmcoreinfo-lists-fix-fix
+++ a/kernel/printk.c
@@ -137,11 +137,13 @@ static char *log_buf = __log_buf;
static int log_buf_len = __LOG_BUF_LEN;
static unsigned logged_chars; /* Number of chars produced since last read+clear operation */
+#ifdef CONFIG_KEXEC
void log_buf_kexec_setup(void)
{
VMCOREINFO_SYMBOL(log_buf);
VMCOREINFO_SYMBOL(log_end);
}
+#endif
static int __init log_buf_len_setup(char *str)
{
_
--
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