linux-kernel - Re: Section mismatch on current git head

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

Message-ID: <20070103060001.GB25433@in.ibm.com>
Date:	Wed, 3 Jan 2007 11:30:01 +0530
From:	Vivek Goyal <vgoyal@...ibm.com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Thomas Meyer <thomas@...3r.de>, linux-kernel@...r.kernel.org,
	Fastboot mailing list <fastboot@...ts.osdl.org>
Subject: Re: Section mismatch on current git head

On Fri, Dec 22, 2006 at 09:47:10AM -0800, Randy Dunlap wrote:
> On Fri, 22 Dec 2006 15:24:41 +0100 Thomas Meyer wrote:
> 
> > Hello.
> >
> > What kind of problem is this:
> > 1.) the one that should be fixed, but also can be ignored or
> > 2.) the one that have to be fixed and ignorance is a bad idea?
> >
> 
> Is this with CONFIG_RELOCATABLE=y?
> There were some patches posted to address section mismatches
> with that config option.  I suppose that they will be in the
> next -mm release (?), so this needs to be retested with
> those patches applied.
> 

Hi Randy,

I have posted some patches. But there are lots of warnings and I am
still working through the rest. Already posted patches are available
in rc2-mm1.

Any help from respective subsystem maintainers is appreciated. :-)

These problems are already present. CONFIG_RELOCATABLE=y just makes
them visible to MODPOST as relocatation information is retained in
vmlinux if CONFIG_RELOCATABLE=y.

Thanks
Vivek
-
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/