linux-kernel - Re: Section mismatch: reference to .init.text: (between 'kthreadd' and 'init_waitqueue

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: <alpine.LFD.0.999.0708021603380.8258@enigma.security.iitk.ac.in>
Date:	Thu, 2 Aug 2007 16:05:24 +0530 (IST)
From:	Satyam Sharma <satyam@...radead.org>
To:	John Sigler <linux.kernel@...e.fr>
cc:	linux-rt-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Section mismatch: reference to .init.text: (between 'kthreadd'
 and 'init_waitqueue_head')



On Thu, 2 Aug 2007, John Sigler wrote:

> Hello,
> 
> I'm trying to build a 2.6.22.1-rt9 kernel for a P3.
> 
> I used 'make xconfig' to create .config
> http://linux.kernel.free.fr/latency/config-2.6.22.1-rt9-adlink
> 
> I get the following warning:
> 
>   LD      vmlinux
>   SYSMAP  System.map
>   SYSMAP  .tmp_System.map
>   MODPOST vmlinux
> WARNING: kernel/built-in.o(.text+0x19152): Section mismatch: reference to
> .init.text: (between 'kthreadd' and 'init_waitqueue_head')

This is a bogus warning, already taken care of in 2.6.23-rc1-latestgit.

> Finally, I note that X86_CMPXCHG64 is no longer defined since its
> specification was changed between 2.6.20 and 2.6.22.
> 
>  config X86_CMPXCHG64
>     bool
> -   depends on !M386 && !M486
> +   depends on X86_PAE
>     default y
> 
> Will this have an impact on spinlocks? RCU? something else?

No idea about this one.
-
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/