linux-kernel - Re: [PATCH] efi_limit_regions triggers link failure when CONFIG

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 24 Nov 2006 17:24:24 +0000
From:	Andy Whitcroft <apw@...dowen.org>
To:	Andi Kleen <ak@...e.de>
CC:	Andrew Morton <akpm@...l.org>,
	Artiom Myaskouvskey <artiom.myaskouvskey@...el.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] efi_limit_regions triggers link failure when CONFIG_EFI
 is not defined

Andi Kleen wrote:
> On Friday 24 November 2006 17:59, Andy Whitcroft wrote:
>> The following patch is needed to get 2.6.19-rc6-mm1 to compile with
>> CONFIG_EFI disabled.  This is the 'shortest' fix.  However, it does
>> appear that there is some overlap with EFI implmentation partly
>> being in e820.c and partly in efi.c.  It might make sense to move
>> everything efi related over to efi.c.
> 
> It compiles here. And the ifdef status hasn't changed at all.

Right, when it was in the function directly the optimiser seems to have
lopped it off nice and early and got rid of the link failure.

> Ah maybe your compiler failed to inline the function so the compiler
> couldn't optimize it away. What compiler were you using? Does it
> go away if you add a "inline" to efi_limit_regions()?

Compiler is as below:

    gcc version 3.3.4 (Debian 1:3.3.4-3)

Yes, making efi_limit_regions() inline also seems to work.  Can we
guarentee it will be inlined though?  I had the feeling that inline was
advisory and if it does not inline then we will get the link failures.

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