linux-kernel - Re: [PATCH] staging: ram_console: Fix section mismatches

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: <4F58F677.8030102@codeaurora.org>
Date:	Thu, 08 Mar 2012 10:12:07 -0800
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Greg KH <gregkh@...uxfoundation.org>
CC:	John Stultz <john.stultz@...aro.org>, linux-kernel@...r.kernel.org,
	Android Kernel Team <kernel-team@...roid.com>
Subject: Re: [PATCH] staging: ram_console: Fix section mismatches

On 03/08/12 09:56, Greg KH wrote:
> On Thu, Mar 08, 2012 at 01:08:04AM -0800, Stephen Boyd wrote:
>> WARNING: vmlinux.o(.text+0x25d5fc): Section mismatch in reference
>> from the function ram_console_driver_probe() to the function
>> .init.text:ram_console_init()
>> The function ram_console_driver_probe() references
>> the function __init ram_console_init().
>> This is often because ram_console_driver_probe lacks a __init
>> annotation or the annotation of ram_console_init is wrong.
>>
>> Mark ram_console_driver_probe() as __devinit because it's a probe
>> function and propagate the __devinit markings to the __init
>> functions the probe calls.
> What .config configuration causes this to happen?  I don't see this here
> in my builds, what am I doing wrong?
>

#
# Android
#
CONFIG_ANDROID=y
# CONFIG_ANDROID_BINDER_IPC is not set
# CONFIG_ASHMEM is not set
# CONFIG_ANDROID_LOGGER is not set
CONFIG_ANDROID_RAM_CONSOLE=y
# CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION is not set
# CONFIG_ANDROID_TIMED_OUTPUT is not set
# CONFIG_ANDROID_LOW_MEMORY_KILLER is not set
# CONFIG_ANDROID_SWITCH is not set
# CONFIG_PHONE is not set


Perhaps you're missing this patch if you're on an ARM compiler?

6e2e340 (ARM: 7324/1: modpost: Fix section warnings for ARM for many
compilers, 2012-02-14)

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

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