linux-kernel - Re: RT Scheduler - BUG_ON (idx >= MAX_RT

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: <1441606598.3529.15.camel@gmail.com>
Date:	Mon, 07 Sep 2015 08:16:38 +0200
From:	Mike Galbraith <umgwanakikbuti@...il.com>
To:	Chinmay V S <cvs268@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-smp@...r.kernel.org, stable-rt@...r.kernel.org
Subject: Re: RT Scheduler - BUG_ON (idx >= MAX_RT_PRIO)

On Mon, 2015-09-07 at 11:00 +0530, Chinmay V S wrote:

> So how could rt_nr_running be non-zero AND active-bitmap NOT have any
> valid bit set?

It can't without being busted.

> Also including the kernel OOPS below.
> Do you see any tell-tale signs in the register-dump/backtrace that can
> point me in the right direction?

Try without the proprietary modules.  You may also want to audit futex
fixes if you can't use a maintained stable tree.  3.2 has a bunch that
3.1 does not.

	-Mike

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