linux-kernel - Re: RCU?: Scheduling while atomic with 3.4.23-rt33

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:	Mon, 18 Feb 2013 12:16:41 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Tim Sander <tim.sander@....com>
cc:	linux-rt-users <linux-rt-users@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: RCU?: Scheduling while atomic with 3.4.23-rt33

On Mon, 18 Feb 2013, Tim Sander wrote:
> Here is a transtribed backtrace for easier reading:
> c0010fac t dump_backtrace
> c022c188 T dump_stack
> c022c71c t __schedule_bug
> c022fb28 t __schedule
> c0230644 t rt_spin_lock_slowlock
> c0230ba8 T rt_spin_lock
> c003a9b8 T __wake_up
> c0052a44 t invoke_rcu_callbacks
> c0053764 T rcu_check_callbacks
> c0026060 T update_process_times

That's due to CONFIG_TINY_PREEMPT_RCU=y. That's a known issue, which
has been fixed in 3.6-rt.

Steven, could you backport that to 3.2/3.4 please ?

Thanks,

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