linux-kernel - Re: THP bug and crash on sparc64 3.8

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]

Date:	Tue, 19 Feb 2013 14:05:42 +0200 (EET)
From:	Meelis Roos <mroos@...ee>
To:	linux-mm@...r.kernel.org
cc:	Linux Kernel list <linux-kernel@...r.kernel.org>,
	sparclinux@...r.kernel.org
Subject: Re: THP bug and crash on sparc64 3.8

	
(Resent to correct cparclinux address)

> I am receiving this with 3.8.0 on Sun E420R (4G RAM, 4 CPUs). System 
> hangs after logging this to syslog. It was busy  running ap at the 
> moment of crash.
> 
> CONFIG_TRANSPARENT_HUGEPAGE=y
> CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y
> # CONFIG_TRANSPARENT_HUGEPAGE_MADVISE is not set
> 
> BUG: sleeping function called from invalid context at mm/slub.c:925
> in_atomic(): 1, irqs_disabled(): 0, pid: 327, name: khugepaged
> 2 locks held by khugepaged/327:
>  #0:  (&mm->mmap_sem){++++++}, at: [<0000000000516964>] 
> khugepaged+0x624/0xf80
>  #1:  (&(&mm->page_table_lock)->rlock){+.+.+.}, at: [<0000000000517078>] 
> khugepaged+0xd38/0xf
> 
> Call Trace:
>  [0000000000488d9c] __might_sleep+0x13c/0x240
>  [000000000051204c] kmem_cache_alloc+0xcc/0x120
>  [000000000044bfc0] tsb_grow+0x80/0x480
>  [000000000044e814] hugetlb_setup+0x14/0xc0
>  [000000000044bcb0] set_pmd_at+0x110/0x120
>  [00000000005170b8] khugepaged+0xd78/0xf80
>  [000000000047e508] kthread+0x88/0xa0
>  [00000000004060a4] ret_from_syscall+0x1c/0x2c
>  [0000000000000000]           (null)
> 

-- 
Meelis Roos (mroos@...ee)      http://www.cs.ut.ee/~mroos/
--
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/