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] [day] [month] [year] [list]
Message-ID: <499356CF.2060706@gmail.com>
Date:	Wed, 11 Feb 2009 23:53:03 +0100
From:	Jiri Slaby <jirislaby@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Brian Gerst <brgerst@...il.com>, Tejun Heo <tj@...nel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] x86: Use linker to offset symbols by __per_cpu_load

On 02/09/2009 10:29 AM, Ingo Molnar wrote:
> * Brian Gerst <brgerst@...il.com> wrote:
> 
>> Impact: cleanup and bug fix
>>
>> Use the linker to create symbols for certain per-cpu variables
>> that are offset by __per_cpu_load.  This allows the removal of
>> the runtime fixup of the GDT pointer, which fixes a bug with
>> resume reported by Jiri Slaby.
>>
>> Signed-off-by: Brian Gerst <brgerst@...il.com>
>> Cc: Jiri Slaby <jirislaby@...il.com>
>> ---
>>  arch/x86/include/asm/percpu.h    |   22 ++++++++++++++++++++++
>>  arch/x86/include/asm/processor.h |    2 ++
>>  arch/x86/kernel/cpu/common.c     |    6 +-----
>>  arch/x86/kernel/head_64.S        |   21 ++-------------------
>>  arch/x86/kernel/vmlinux_64.lds.S |    8 ++++++++
>>  5 files changed, 35 insertions(+), 24 deletions(-)
> 
> applied to tip/core/percpu, thanks!
> 
> Also added these tags:
> 
> Reported-by: Jiri Slaby <jirislaby@...il.com>
> Acked-by: Jiri Slaby <jirislaby@...il.com>

Ok, fixes the problem for me, thanks.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ