linux-kernel - Re: mmotm 2008-10-02-16-17 uploaded

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]

Date:	Wed, 8 Oct 2008 11:50:24 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	yinghai@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: mmotm 2008-10-02-16-17 uploaded


* Andrew Morton <akpm@...ux-foundation.org> wrote:

> > > could be merging problem again.
> > > 
> > > please check in arch/x86/kernel/vmliux_64.lds.S
> > > 
> > > it should be like 
> > > 
> > >   __con_initcall_end = .;
> > >   __x86_cpu_dev_start = .;
> > >   .x86_cpu_dev.init : AT(ADDR(.x86_cpu_dev.init) - LOAD_OFFSET) {
> > >         *(.x86_cpu_dev.init)
> > >   }
> > >   __x86_cpu_dev_end = .;
> > > 
> > >   DYN_ARRAY_INIT(8)
> > > 
> > >   SECURITY_INIT
> 
> The above is what's presently in Ingo's "tip" tree.
> 
> > Oh, yes. like this.
> > ==
> >  __con_initcall_end = .;
> >   __x86_cpu_dev_start = .;
> >   .x86_cpu_dev.init : AT(ADDR(.x86_cpu_dev.init) - LOAD_OFFSET) {
> >         *(.x86_cpu_dev.init)
> >   }
> >   SECURITY_INIT
> >   __x86_cpu_dev_end = .;
> > ==
> > 
> > I'll try next version when it comes.
> 
> If that fixes it then Ingo's tree will need fixing too, I suppose.

it should be:

  __x86_cpu_dev_end = .;

  DYN_ARRAY_INIT(8)

  SECURITY_INIT

and that's what it is in -tip. Am i missing something?

	Ingo
--
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/