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: <CAE9FiQUV8UsqAe3WJz02a9oiVw8hygyQsZzwuM782s-8hV92Nw@mail.gmail.com>
Date:	Tue, 25 Dec 2012 12:57:28 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7 00/27] x86, boot, 64bit: Add support for loading
 ramdisk and bzImage above 4G

On Mon, Dec 24, 2012 at 3:56 PM, H. Peter Anvin <hpa@...or.com> wrote:
> On 12/23/2012 10:00 AM, Yinghai Lu wrote:
>> On Sun, Dec 23, 2012 at 6:33 AM, H. Peter Anvin <hpa@...or.com> wrote:
>>> Explanation please?
>>>
>>
>> you have following change in the patch
>>
>>         /* Finally jump to run C code and to be on real kernel address
>>          * Since we are running on identity-mapped space we have to jump
>>          * to the full 64bit address, this is only possible as indirect
>>          * jump.  In addition we need to ensure %cs is set so we make this
>> -        * a far return.
>> +        * a far jump.
>>          */
>> -       movq    initial_code(%rip),%rax
>>         pushq   $0              # fake return address to stop unwinder
>> -       pushq   $__KERNEL_CS    # set correct cs
>> -       pushq   %rax            # target address in negative space
>> -       lretq
>> +       /* gas 2.22 is buggy and mis-assembles ljmpq */
>> +       rex64 ljmp *initial_code(%rip)
>>
>>  #ifdef CONFIG_HOTPLUG_CPU
>>  /*
>>
>> remove that change, AMD systems works again.
>>
>
> That is not an explanation.

what do you mean?

Konrad reported the problem, and I dig out one AMD system and
duplicated the problem.
and found the patch cause the problem, then add serial out in the
file, and turns out
that reset happen just after those lines, so I revert those lines, and
it boots well again.

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