Kees Cook writes:
> On Sun, Jan 4, 2015 at 8:28 PM, Rusty Russell wrote:
>> Oded Gabbay writes:
>>> On 12/24/2014 01:01 AM, Rusty Russell wrote:
Oded Gabbay writes:
> I didn't say it doesn't always work.
> The actual thing that doesn't work is the define symbol_get and only in a
Kees Cook keesc...@chromium.org writes:
On Sun, Jan 4, 2015 at 8:28 PM, Rusty Russell ru...@rustcorp.com.au wrote:
Oded Gabbay oded.gab...@amd.com writes:
On 12/24/2014 01:01 AM, Rusty Russell wrote:
Oded Gabbay oded.gab...@amd.com writes:
I didn't say it doesn't always work.
The actual
On 01/16/2015 02:27 AM, Kees Cook wrote:
> On Sun, Jan 4, 2015 at 8:28 PM, Rusty Russell wrote:
>> Oded Gabbay writes:
>>> On 12/24/2014 01:01 AM, Rusty Russell wrote:
Oded Gabbay writes:
> I didn't say it doesn't always work.
> The actual thing that doesn't work is the define
On 01/16/2015 02:27 AM, Kees Cook wrote:
On Sun, Jan 4, 2015 at 8:28 PM, Rusty Russell ru...@rustcorp.com.au wrote:
Oded Gabbay oded.gab...@amd.com writes:
On 12/24/2014 01:01 AM, Rusty Russell wrote:
Oded Gabbay oded.gab...@amd.com writes:
I didn't say it doesn't always work.
The actual
On Sun, Jan 4, 2015 at 8:28 PM, Rusty Russell wrote:
> Oded Gabbay writes:
>> On 12/24/2014 01:01 AM, Rusty Russell wrote:
>>> Oded Gabbay writes:
I didn't say it doesn't always work.
The actual thing that doesn't work is the define symbol_get and only in a
specific case of 32bit
On Sun, Jan 4, 2015 at 8:28 PM, Rusty Russell ru...@rustcorp.com.au wrote:
Oded Gabbay oded.gab...@amd.com writes:
On 12/24/2014 01:01 AM, Rusty Russell wrote:
Oded Gabbay oded.gab...@amd.com writes:
I didn't say it doesn't always work.
The actual thing that doesn't work is the define
On Tue, Jan 6, 2015 at 2:58 PM, Rusty Russell wrote:
> Kees Cook writes:
>> On Sun, Jan 4, 2015 at 8:28 PM, Rusty Russell 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
On Tue, Jan 6, 2015 at 2:58 PM, Rusty Russell ru...@rustcorp.com.au wrote:
Kees Cook keesc...@chromium.org writes:
On Sun, Jan 4, 2015 at 8:28 PM, Rusty Russell ru...@rustcorp.com.au wrote:
Kees, as far as I can tell you need another 0-terminated vmlinux.relocs
section for weak symbols. These
On 01/07/2015 12:58 AM, Rusty Russell wrote:
> Kees Cook writes:
>> On Sun, Jan 4, 2015 at 8:28 PM, Rusty Russell 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:
On 01/07/2015 12:58 AM, Rusty Russell wrote:
Kees Cook keesc...@chromium.org writes:
On Sun, Jan 4, 2015 at 8:28 PM, Rusty Russell ru...@rustcorp.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
Kees Cook writes:
> On Sun, Jan 4, 2015 at 8:28 PM, Rusty Russell 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?
On Sun, Jan 4, 2015 at 8:28 PM, Rusty Russell wrote:
> Oded Gabbay writes:
>> On 12/24/2014 01:01 AM, Rusty Russell wrote:
>>> Oded Gabbay writes:
I didn't say it doesn't always work.
The actual thing that doesn't work is the define symbol_get and only in a
specific case of 32bit
On Sun, Jan 4, 2015 at 8:28 PM, Rusty Russell ru...@rustcorp.com.au wrote:
Oded Gabbay oded.gab...@amd.com writes:
On 12/24/2014 01:01 AM, Rusty Russell wrote:
Oded Gabbay oded.gab...@amd.com writes:
I didn't say it doesn't always work.
The actual thing that doesn't work is the define
Kees Cook keesc...@chromium.org writes:
On Sun, Jan 4, 2015 at 8:28 PM, Rusty Russell ru...@rustcorp.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
Oded Gabbay writes:
> On 12/24/2014 01:01 AM, Rusty Russell wrote:
>> Oded Gabbay writes:
>>> I didn't say it doesn't always work.
>>> The actual thing that doesn't work is the define symbol_get and only in a
>>> specific case of 32bit kernel AND CONFIG_MODULES is unset AND
>>>
Oded Gabbay oded.gab...@amd.com writes:
On 12/24/2014 01:01 AM, Rusty Russell wrote:
Oded Gabbay oded.gab...@amd.com writes:
I didn't say it doesn't always work.
The actual thing that doesn't work is the define symbol_get and only in a
specific case of 32bit kernel AND CONFIG_MODULES is unset
On 12/25/2014 02:31 PM, Christian König wrote:
Am 22.12.2014 um 20:18 schrieb Oded Gabbay:
On 12/22/2014 09:00 PM, Andi Kleen wrote:
On Mon, Dec 22, 2014 at 10:49:40AM -0800, Andi Kleen wrote:
On Mon, Dec 22, 2014 at 11:58:43AM -0500, Alex Deucher wrote:
On Mon, Dec 22, 2014 at 6:11 AM,
On 12/25/2014 02:31 PM, Christian König wrote:
Am 22.12.2014 um 20:18 schrieb Oded Gabbay:
On 12/22/2014 09:00 PM, Andi Kleen wrote:
On Mon, Dec 22, 2014 at 10:49:40AM -0800, Andi Kleen wrote:
On Mon, Dec 22, 2014 at 11:58:43AM -0500, Alex Deucher wrote:
On Mon, Dec 22, 2014 at 6:11 AM,
Am 22.12.2014 um 20:18 schrieb Oded Gabbay:
On 12/22/2014 09:00 PM, Andi Kleen wrote:
On Mon, Dec 22, 2014 at 10:49:40AM -0800, Andi Kleen wrote:
On Mon, Dec 22, 2014 at 11:58:43AM -0500, Alex Deucher wrote:
On Mon, Dec 22, 2014 at 6:11 AM, Oded Gabbay wrote:
amdkfd driver can be compiled
Am 22.12.2014 um 20:18 schrieb Oded Gabbay:
On 12/22/2014 09:00 PM, Andi Kleen wrote:
On Mon, Dec 22, 2014 at 10:49:40AM -0800, Andi Kleen wrote:
On Mon, Dec 22, 2014 at 11:58:43AM -0500, Alex Deucher wrote:
On Mon, Dec 22, 2014 at 6:11 AM, Oded Gabbay oded.gab...@amd.com wrote:
amdkfd
Oded Gabbay writes:
> I didn't say it doesn't always work.
> The actual thing that doesn't work is the define symbol_get and only in a
> specific case of 32bit kernel AND CONFIG_MODULES is unset AND
> CONFIG_RANDOMIZE_BASE is set.
> The define in that case is:
> #define symbol_get(x) ({ extern
Oded Gabbay oded.gab...@amd.com writes:
I didn't say it doesn't always work.
The actual thing that doesn't work is the define symbol_get and only in a
specific case of 32bit kernel AND CONFIG_MODULES is unset AND
CONFIG_RANDOMIZE_BASE is set.
The define in that case is:
#define symbol_get(x)
On 12/22/2014 09:00 PM, Andi Kleen wrote:
> On Mon, Dec 22, 2014 at 10:49:40AM -0800, Andi Kleen wrote:
>> On Mon, Dec 22, 2014 at 11:58:43AM -0500, Alex Deucher wrote:
>>> On Mon, Dec 22, 2014 at 6:11 AM, Oded Gabbay wrote:
amdkfd driver can be compiled only in 64-bit kernel. Therefore,
On Mon, Dec 22, 2014 at 10:49:40AM -0800, Andi Kleen wrote:
> On Mon, Dec 22, 2014 at 11:58:43AM -0500, Alex Deucher wrote:
> > On Mon, Dec 22, 2014 at 6:11 AM, Oded Gabbay wrote:
> > > amdkfd driver can be compiled only in 64-bit kernel. Therefore, there is
> > > no
> > > point in trying to
On Mon, Dec 22, 2014 at 11:58:43AM -0500, Alex Deucher wrote:
> On Mon, Dec 22, 2014 at 6:11 AM, Oded Gabbay wrote:
> > amdkfd driver can be compiled only in 64-bit kernel. Therefore, there is no
> > point in trying to initialize amdkfd in 32-bit kernel.
> >
> > In addition, in case of specific
On Mon, Dec 22, 2014 at 6:11 AM, Oded Gabbay wrote:
> amdkfd driver can be compiled only in 64-bit kernel. Therefore, there is no
> point in trying to initialize amdkfd in 32-bit kernel.
>
> In addition, in case of specific configuration of 32-bit kernel, no modules
> and
> random kernel base,
amdkfd driver can be compiled only in 64-bit kernel. Therefore, there is no
point in trying to initialize amdkfd in 32-bit kernel.
In addition, in case of specific configuration of 32-bit kernel, no modules and
random kernel base, the symbol_request function doesn't work as expected - It
doesn't
amdkfd driver can be compiled only in 64-bit kernel. Therefore, there is no
point in trying to initialize amdkfd in 32-bit kernel.
In addition, in case of specific configuration of 32-bit kernel, no modules and
random kernel base, the symbol_request function doesn't work as expected - It
doesn't
On Mon, Dec 22, 2014 at 6:11 AM, Oded Gabbay oded.gab...@amd.com wrote:
amdkfd driver can be compiled only in 64-bit kernel. Therefore, there is no
point in trying to initialize amdkfd in 32-bit kernel.
In addition, in case of specific configuration of 32-bit kernel, no modules
and
random
On Mon, Dec 22, 2014 at 11:58:43AM -0500, Alex Deucher wrote:
On Mon, Dec 22, 2014 at 6:11 AM, Oded Gabbay oded.gab...@amd.com wrote:
amdkfd driver can be compiled only in 64-bit kernel. Therefore, there is no
point in trying to initialize amdkfd in 32-bit kernel.
In addition, in case of
On Mon, Dec 22, 2014 at 10:49:40AM -0800, Andi Kleen wrote:
On Mon, Dec 22, 2014 at 11:58:43AM -0500, Alex Deucher wrote:
On Mon, Dec 22, 2014 at 6:11 AM, Oded Gabbay oded.gab...@amd.com wrote:
amdkfd driver can be compiled only in 64-bit kernel. Therefore, there is
no
point in trying
On 12/22/2014 09:00 PM, Andi Kleen wrote:
On Mon, Dec 22, 2014 at 10:49:40AM -0800, Andi Kleen wrote:
On Mon, Dec 22, 2014 at 11:58:43AM -0500, Alex Deucher wrote:
On Mon, Dec 22, 2014 at 6:11 AM, Oded Gabbay oded.gab...@amd.com wrote:
amdkfd driver can be compiled only in 64-bit kernel.
32 matches
Mail list logo