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]

Date:	Mon, 7 Sep 2015 12:28:18 +0530
From:	Chinmay V S <cvs268@...il.com>
To:	Mike Galbraith <umgwanakikbuti@...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)

Thanks for your quick response Mike.

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

I see that futex.c has 17 patches in 3.2.y that are missing in my tree.
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/kernel/futex.c?h=linux-3.2.y

Will apply these patches and kick-off a run today.
It takes upto 2days to reproduce this RT-scheduler BUG().

Also, in one of the earlier runs to reproduce, i had enabled
CONFIG_CC_STACKPROTECTOR
CONFIG_STRICT_DEVMEM
but there weren't any additional logs indicating illegal writes to memory.
Kernel OOPS was similar to the one in the original email in this thread.

To catch the "culprit" in the middle of busting the scheduler's
internal data structures, what would be the recommended debug
mechanisms (or config options) that i can try?

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