linux-kernel - Re: [origin tree boot hang] lockup in key_schedule

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: <1252787226.13780.1.camel@dhcp231-106.rdu.redhat.com>
Date:	Sat, 12 Sep 2009 16:27:06 -0400
From:	Eric Paris <eparis@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	James Morris <jmorris@...ei.org>, linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	dhowells@...hat.com
Subject: Re: [origin tree boot hang] lockup in key_schedule_gc()

On Sat, 2009-09-12 at 15:58 +0200, Ingo Molnar wrote:
> here's a new crash related to security changes - a boot lockup on a 
> testbox:
> 
> Pid: 5, comm: events/0 Tainted: G        W  (2.6.31-tip-02301-g1c11bd7-dirty #13102) System Product Name
> EIP: 0060:[<c104ad77>] EFLAGS: 00000046 CPU: 0
> EIP is at trace_hardirqs_off_caller+0x30/0x9a
> EAX: 00000002 EBX: f70431c0 ECX: c18c8e58 EDX: c10138ce
> ESI: c10138ce EDI: 00000002 EBP: f7051ddc ESP: f7051dd4
>  DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
> CR0: 8005003b CR2: b745e530 CR3: 3618f000 CR4: 000006d0
> DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: c210fa6c
> DR6: ffff0ff0 DR7: 00000400
> Call Trace:
>  [<c104adec>] trace_hardirqs_off+0xb/0xd
>  [<c10138ce>] default_send_IPI_mask_logical+0xd2/0xe3
>  [<c1013759>] default_send_IPI_all+0x27/0x67
>  [<c1013a97>] arch_trigger_all_cpu_backtrace+0x30/0x54
>  [<c1060c46>] __rcu_pending+0x49/0x113
>  [<c1060d2d>] rcu_check_callbacks+0x1d/0x9c
>  [<c103390c>] update_process_times+0x29/0x3e
>  [<c104713c>] tick_periodic+0x6a/0x6c
>  [<c1047152>] tick_handle_periodic+0x14/0x6a
>  [<c1013463>] smp_apic_timer_interrupt+0x63/0x73
>  [<c100302f>] apic_timer_interrupt+0x2f/0x40
>  [<c15fdaaa>] ? _spin_unlock_irqrestore+0x3d/0x41
>  [<c103a685>] __queue_work+0x2b/0x30
>  [<c103a6d1>] queue_work_on+0x2c/0x36
>  [<c103a7b2>] queue_work+0x13/0x15
>  [<c103a7c8>] schedule_work+0x14/0x16
>  [<c125178a>] key_schedule_gc+0x28/0x4e
>  [<c1251917>] key_garbage_collector+0x167/0x180
>  [<c103a004>] run_workqueue+0xfb/0x1c4
>  [<c1039fe5>] ? run_workqueue+0xdc/0x1c4
>  [<c12517b0>] ? key_garbage_collector+0x0/0x180
>  [<c103a146>] worker_thread+0x79/0x85
>  [<c103d3e3>] ? autoremove_wake_function+0x0/0x38
>  [<c103a0cd>] ? worker_thread+0x0/0x85
>  [<c103d1d2>] kthread+0x65/0x6a
>  [<c103d16d>] ? kthread+0x0/0x6a
>  [<c1003267>] kernel_thread_helper+0x7/0x10
> Pid: 5, comm: events/0 Tainted: G        W  2.6.31-tip-02301-g1c11bd7-dirty #13102
> 
> config and bootlog attached.

Adding dhowells, the keys maintainer, this one certainly isn't obvious
to me off hand.

-Eric

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