linux-kernel - Re: general protection fault: 0000 [#1] PREEMPT SMP

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, 24 Aug 2010 10:58:02 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	linux-kernel@...r.kernel.org
Subject: Re: general protection fault: 0000 [#1] PREEMPT SMP

Hello,

On 08/13/2010 03:47 PM, Sergey Senozhatsky wrote:
> [   29.943019]  [<ffffffff81065893>] lock_acquire+0x97/0xb6
..
> [   29.943257]  [<ffffffff8137568d>] _raw_spin_lock_irqsave+0x4e/0x60
..
> [   29.943376]  [<ffffffff8137145b>] percpu_counter_hotcpu_callback+0x3e/0x93

It's getting gpf at spin_lock_irqsave(&fbc->lock) in
percpu_counter_hotplug_callback().  percpu_counter keeps track of all
the allocated percpu counters and walk them on cpu up/down events.
It's most likely one of its users freed or corrupted the percpu
counter structure without properly destroying it.  Adding debugobj is
probably the best way to track down the offending user.

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/