linux-kernel - Re: linux-next: build failure after merge of the final tree (rr tree related)

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] [day] [month] [year] [list]

Message-Id: <201006041506.59887.rusty@rustcorp.com.au>
Date:	Fri, 4 Jun 2010 15:06:59 +0930
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (rr tree related)

On Fri, 4 Jun 2010 02:19:33 pm Stephen Rothwell wrote:
> Hi Rusty,
> 
> After merging the final tree, today's linux-next build (powerpc
> ppc44x_defconfig) failed like this:
> 
> kernel/module.c: In function 'post_relocation':
> kernel/module.c:2526: error: 'struct module' has no member named 'percpu_size'
> 
> Caused by commit fc77407bc287ed250f9355fda435df5f78b45885 ("module:
> simplify per-cpu handling a little").
> 
> This build has CONFIG_SMP not set

Actually, I think that cleanup is broken.  If someone were to have relocations
inside their per-cpu area, the relocation code would smash something random.

So, a doubly bad idea.  I've dropped the commit.

Thanks!
Rusty.
--
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/