linux-kernel - Re: Early boot panic on machine with lots of memory

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: <20120618223203.GE32733@google.com>
Date:	Mon, 18 Jun 2012 15:32:03 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Sasha Levin <levinsasha928@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	David Miller <davem@...emloft.net>, hpa@...ux.intel.com,
	linux-mm <linux-mm@...ck.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Early boot panic on machine with lots of memory

On Thu, Jun 14, 2012 at 11:50:40AM +0200, Sasha Levin wrote:
> On Thu, 2012-06-14 at 12:20 +0900, Tejun Heo wrote:
> > On Wed, Jun 13, 2012 at 11:38:55PM +0200, Sasha Levin wrote:
> > > Hi all,
> > > 
> > > I'm seeing the following when booting a KVM guest with 65gb of RAM, on latest linux-next.
> > > 
> > > Note that it happens with numa=off.
> > > 
> > > [    0.000000] BUG: unable to handle kernel paging request at ffff88102febd948
> > > [    0.000000] IP: [<ffffffff836a6f37>] __next_free_mem_range+0x9b/0x155
> > 
> > Can you map it back to the source line please?
> 
> mm/memblock.c:583
> 
>                         phys_addr_t r_start = ri ? r[-1].base + r[-1].size : 0;
>   97:   85 d2                   test   %edx,%edx
>   99:   74 08                   je     a3 <__next_free_mem_range+0xa3>
>   9b:   49 8b 48 f0             mov    -0x10(%r8),%rcx
>   9f:   49 03 48 e8             add    -0x18(%r8),%rcx
> 
> It's the deref on 9b (r8=ffff88102febd958).

* Can you please post disassembly of the whole function?  It seems
  like rsv->regions[] was corrupt.  I want to verify other registers
  too.

* Can you please try the following patch?

  https://lkml.org/lkml/2012/6/15/510

Thanks.

-- 
tejun
--
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/