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: <3E5A0FA7E9CA944F9D5414FEC6C71220528C2DFF@ORSMSX105.amr.corp.intel.com>
Date:	Wed, 13 Mar 2013 15:22:43 +0000
From:	"Yu, Fenghua" <fenghua.yu@...el.com>
To:	"dave@...ux.vnet.ibm.com" <dave@...ux.vnet.ibm.com>,
	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
	"hpa@...ux.intel.com" <hpa@...ux.intel.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [3.9-rc1] Bug in bootup code or debug code?

> -----Original Message-----
> From: Tetsuo Handa [mailto:penguin-kernel@...ove.SAKURA.ne.jp]
> Sent: Wednesday, March 13, 2013 6:24 AM
> To: Yu, Fenghua; hpa@...ux.intel.com
> Cc: linux-kernel@...r.kernel.org
> Subject: Re: [3.9-rc1] Bug in bootup code or debug code?
> 
> Tetsuo Handa wrote:
> > Tetsuo Handa wrote:
> > > Hello.
> > >
> > > I can boot linux-next-20130205 using kernel config at
> > > http://I-love.SAKURA.ne.jp/tmp/config-3.8-rc6-next-20130205 .
> > > But I get VMware's virtual machine kernel stack fault (hardware
> reset) as soon
> > > as kernel is loaded if CONFIG_DEBUG_VIRTUAL=y is added to the
> config above.
> > >
> > > Since I don't get kernel stack fault if CONFIG_DEBUG_VIRTUAL=y is
> added to
> > > kernel config generated by "make allnoconfig", I guess something is
> wrong with
> > > code which is executed at very early stage of bootup.
> > >
> > > Any clue?
> > >
> > > Regards.
> > >
> >
> > This bug is not yet fixed as of 3.9-rc1.
> > Should I run git bisect?
> >
> > Regards.
> >
> 
> I found the location of "hardware reset" trigger.
> 
> It is __pa_symbol(&boot_params) call, for I don't encounter "hardware
> reset" if
> I remove the "//" from below debug patch.
> 
> This bug is not yet fixed as of 3.9.0-rc2-00188-g6c23cbb .
> 
> --- a/arch/x86/kernel/microcode_intel_early.c
> +++ b/arch/x86/kernel/microcode_intel_early.c
> @@ -741,7 +741,9 @@ load_ucode_intel_bsp(void)
>  #ifdef CONFIG_X86_32
>         struct boot_params *boot_params_p;
> 
> +       //while (1);
>         boot_params_p = (struct boot_params *)__pa_symbol(&boot_params);
> +       while (1);
>         ramdisk_image = boot_params_p->hdr.ramdisk_image;
>         ramdisk_size  = boot_params_p->hdr.ramdisk_size;
>         initrd_start_early = ramdisk_image;

Tetsuo and Dave,

That's the place where we suspected to cause the problem.

My question is: how to access global variable in linear mode in virtualization? __pa_symbol() is not a problem for native.

Thanks.

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