linux-kernel - Re: [BUG] 2.6.25-rc2-mm1 - Kernel panic while bootup caused by signal_group

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:	Thu, 28 Feb 2008 14:13:23 +0100
From:	Cedric Le Goater <clg@...ibm.com>
To:	Rik van Riel <riel@...hat.com>
CC:	Oleg Nesterov <oleg@...sign.ru>,
	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, roland@...hat.com,
	Andy Whitcroft <apw@...dowen.org>,
	Balbir Singh <balbir@...ux.vnet.ibm.com>
Subject: Re: [BUG] 2.6.25-rc2-mm1 - Kernel panic while bootup caused by signal_group_exit()

Hello !

Rik van Riel wrote:
> On Wed, 20 Feb 2008 23:04:40 +0300
> Oleg Nesterov <oleg@...sign.ru> wrote:
> 
>> Yes, please look at http://marc.info/?t=120309840500006
>>
>> Btw. The bug in tty_io.c _can_ explain this trace, but it would be nice
>> to ensure we don't have other problems. Could you try this
>>
>> 	http://marc.info/?l=linux-kernel&m=120352655031911
>>
>> patch?
> 
> Fun.  With that debugging patch applied, the oops on boot no longer
> happens...
> 
> No, I have no idea why...

It also fixed a oops at boot time for me. Here's a warning I got with oleg patch.

Thanks,

C.

WARNING: at /home/legoater/linux/2.6.25-rc2-mm1/kernel/pid.c:213 put_pid+0x4b/0x82()
Modules linked in: tg3 sg joydev ext3 jbd uhci_hcd ohci_hcd ehci_hcd
Pid: 1, comm: init Not tainted 2.6.25-rc2-mm1 #6

Call Trace:
 [<ffffffff8022f0a1>] warn_on_slowpath+0x58/0x85
 [<ffffffff8024b87d>] ? trace_hardirqs_on+0xd/0xf
 [<ffffffff8024b84c>] ? trace_hardirqs_on_caller+0xf2/0x116
 [<ffffffff8024b87d>] ? trace_hardirqs_on+0xd/0xf
 [<ffffffff8024b84c>] ? trace_hardirqs_on_caller+0xf2/0x116
 [<ffffffff8023fb0f>] put_pid+0x4b/0x82
 [<ffffffff802ccd6e>] ? proc_delete_inode+0x0/0x4f
 [<ffffffff802ccd90>] proc_delete_inode+0x22/0x4f
 [<ffffffff802ccd6e>] ? proc_delete_inode+0x0/0x4f
 [<ffffffff802a0826>] generic_delete_inode+0xb8/0x138
 [<ffffffff8029fd5d>] iput+0x7c/0x80
 [<ffffffff8029d835>] dentry_iput+0xa3/0xbb
 [<ffffffff8029d8ea>] d_kill+0x21/0x42
 [<ffffffff8029ebee>] dput+0x114/0x125
 [<ffffffff802cefe0>] proc_flush_task+0x125/0x28f
 [<ffffffff8024b87d>] ? trace_hardirqs_on+0xd/0xf
 [<ffffffff802312a5>] release_task+0x24/0x331
 [<ffffffff80231ca1>] do_wait+0x6ef/0xa99
 [<ffffffff80227b43>] ? default_wake_function+0x0/0xf
 [<ffffffff802320dc>] sys_wait4+0x91/0xab
 [<ffffffff8020b21b>] system_call_after_swapgs+0x7b/0x80

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