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] [day] [month] [year] [list]

Message-ID: <CAOPOgtAJg_ZOUr+PepEgAS3_Qn4C__c1UNy93AHCpwQX=ztPgA@mail.gmail.com>
Date:	Mon, 7 Sep 2015 15:08:35 +0530
From:	Sujit K M <sjt.kar@...il.com>
To:	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, Sep 7, 2015 at 11:00 AM, Chinmay V S <cvs268@...il.com> wrote:
> Hello everyone,
>
> TL;DR: In Linux RT scheduler, how can rt_nr_running be non-zero AND
> active-bitmap NOT have any valid bit set?
>
> Details:
> Recently i encountered the following BUG() within the realtime
> scheduler (sched_rt.c) on 3.1.10 kernel.
> [101640.492840] kernel BUG at kernel/sched_rt.c:1126!
>
> This turns out to be
> 1126         BUG_ON(idx >= MAX_RT_PRIO);

The reason for the stack trace is given below.
http://www.spinics.net/lists/newbies/msg08889.html





-- 
-- Sujit K M

blog(http://kmsujit.blogspot.com/)
--
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/