linux-kernel - Re: [PROBLEM] 2.6.22-rc2 panics on x86-64 with slub

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-next>] [day] [month] [year] [list]

Date:	Sun, 20 May 2007 23:35:05 +1000 (EST)
From:	Srihari Vijayaraghavan <sriharivijayaraghavan@...oo.com.au>
To:	Christoph Lameter <clameter@....com>
Cc:	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PROBLEM] 2.6.22-rc2 panics on x86-64 with slub

--- Srihari Vijayaraghavan <sriharivijayaraghavan@...oo.com.au> wrote:
> --- Christoph Lameter <clameter@....com> wrote:
> > On Sun, 20 May 2007, Srihari Vijayaraghavan wrote:
> > 
> > > Code: 0f ob eb fe 48 8b 1b 48 8b 0x 0f 18 08 48 81 fb 60 cb 51 80
> > > RIP [...] slab_sysfs_init+0x49/0x98
> > > RSP [...]
> > > kernel panic - not syncing: Attempted to kill init!
> > 
> > sysfs? If you build without CONFIG_SLUB_DEBUG then SLUB will not use 
> > sysfs. You can switch that off in the embedded section.
> 
> Fair enough. Would you the section name it appears in 'menuconfig'?

[Sorry for replying to my own email. I've made some progress since then, so
here goes ...]

Sorry for the noise. I've discovered it under "General setup - Configure
standard kernel features (for small systems)".

With no CONFIG_SLUB_DEBUG, things have slightly improved. No more panic. Good.
Serial console is working. Good. But there is another problem:

...
Freeing unused kernel memory: 308k freed
BUG: spinlock bad magic on CPU#1, init/1
 lock: ffff81011ec0a100, .magic: ffff8101, .owner: <none>/-1, .owner_cpu: -1

Call Trace:
 [<ffffffff802fc516>] _raw_spin_lock+0x22/0xf6
 [<ffffffff8026f684>] vma_adjust+0x219/0x454
 [<ffffffff8026f684>] vma_adjust+0x219/0x454
 [<ffffffff8026fe0d>] vma_merge+0x147/0x1f4
 [<ffffffff80270b55>] do_mmap_pgoff+0x414/0x7c7
 [<ffffffff8040aa34>] _spin_unlock_irq+0x24/0x27
 [<ffffffff8020f528>] sys_mmap+0xe5/0x110
 [<ffffffff80209dde>] system_call+0x7e/0x83

ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
...
PM: Adding info for No Bus:vcsa1
BUG: spinlock lockup on CPU#0, sh/385, ffff81011ca8ffc0

Call Trace:
 [<ffffffff802fc5c3>] _raw_spin_lock+0xcf/0xf6
 [<ffffffff80273352>] anon_vma_unlink+0x1c/0x68
 [<ffffffff80273352>] anon_vma_unlink+0x1c/0x68
 [<ffffffff8026ddf4>] free_pgtables+0x69/0xc3
 [<ffffffff8026f0c0>] exit_mmap+0x91/0xeb
 [<ffffffff802295a1>] mmput+0x45/0xb8
 [<ffffffff80288ad8>] flush_old_exec+0x65f/0x941
 [<ffffffff80284c04>] vfs_read+0x13f/0x153
 [<ffffffff802b5a33>] load_elf_binary+0x0/0x197f
 [<ffffffff802b5e93>] load_elf_binary+0x460/0x197f
 [<ffffffff80263557>] __alloc_pages+0x72/0x2d4
 [<ffffffff802b5a33>] load_elf_binary+0x0/0x197f
 [<ffffffff80287d08>] search_binary_handler+0xc4/0x25f
 [<ffffffff80289834>] do_execve+0x188/0x231
 [<ffffffff80208bf7>] sys_execve+0x36/0x8a
 [<ffffffff8020a1d7>] stub_execve+0x67/0xb0

It just simply hangs there. With slab all is well, of course.

(If you want me to activate all kernel debugging options, do advise, I'm happy
to do that. Nothing changed in ref to my .config from the past email save the
CONFIG_SLUB_DEBUG is gone now.)

The dmesg is attached for your reference.

Thanks


      ___________________________________________________________________________________
How would you spend $50,000 to create a more sustainable environment in Australia?  Go to Yahoo!7 Answers and share your idea.
http://advision.webevents.yahoo.com/aunz/lifestyle/answers/y7ans-babp_reg.html

View attachment "dmesg-2.6.22-slub.txt" of type "text/plain" (20067 bytes)