[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54B26547.2030400@amd.com>
Date: Sun, 11 Jan 2015 13:57:59 +0200
From: Oded Gabbay <oded.gabbay@....com>
To: Kees Cook <keescook@...omium.org>
CC: Rusty Russell <rusty@...tcorp.com.au>,
Andi Kleen <ak@...ux.intel.com>,
Alex Deucher <alexdeucher@...il.com>,
"H. Peter Anvin" <hpa@...or.com>,
"Dana Elifaz" <Dana.Elifaz@....com>,
LKML <linux-kernel@...r.kernel.org>,
"Maling list - DRI developers" <dri-devel@...ts.freedesktop.org>,
Alexander Deucher <Alexander.Deucher@....com>,
LKP ML <lkp@...org>
Subject: Re: [LKP] [PATCH] drm/radeon: Try to init amdkfd only if 64 bit kernel
On 01/07/2015 12:58 AM, Rusty Russell wrote:
> Kees Cook <keescook@...omium.org> writes:
>> On Sun, Jan 4, 2015 at 8:28 PM, Rusty Russell <rusty@...tcorp.com.au> wrote:
>>> Kees, as far as I can tell you need another 0-terminated vmlinux.relocs
>>> section for weak symbols. These should not be relocated if already 0.
>>
>> A few questions:
>>
>> Why doesn't this break on 32-bit without kASLR? 32-bit does relocation
>> by default, even without CONFIG_RANDOMIZE_BASE.
>
> Well, the offset was 0 until I removed CONFIG_HIBERNATE.
>
>> Are there any symbols that are NULL that aren't weak? I'd expect all
>> strong symbols to have non-zero offsets, but I must be
>> misunderstanding something here.
>
> I don't think there would be. Anyway, you might be able to filter them
> out in x86/tools/relocs itself.
>
> Cheers,
> Rusty.
>
Hi Kees,
Did you had time to look at the problem ?
Oded
--
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/
Powered by blists - more mailing lists