linux-kernel - Re: rcu: eqs related warnings in linux-next

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:	Sat, 29 Sep 2012 14:25:04 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Sasha Levin <levinsasha928@...il.com>
Cc:	paulmck@...ux.vnet.ibm.com, Dave Jones <davej@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: rcu: eqs related warnings in linux-next

2012/9/29 Sasha Levin <levinsasha928@...il.com>:
> Maybe I could help here a bit.
>
> lappy linux # addr2line -i -e vmlinux ffffffff8111d45f
> /usr/src/linux/kernel/timer.c:549
> /usr/src/linux/include/linux/jump_label.h:101
> /usr/src/linux/include/trace/events/timer.h:44
> /usr/src/linux/kernel/timer.c:601
> /usr/src/linux/kernel/timer.c:734
> /usr/src/linux/kernel/timer.c:886
>
> Which means that it was about to:
>
>         debug_object_activate(timer, &timer_debug_descr);

I can't find anything in the debug object code that might fault.
I was suspecting some per cpu allocated memory: per cpu allocation
sometimes use vmalloc
which uses lazy paging using faults. But I can't find such thing there.

May be there is some faulting specific to KVM...
--
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/