linux-kernel - Re: sched_yield() call on Linux Kernel 2.6.39 is not behaving correct

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: <CAH86sKJnx1wgtkZ-S0QHcRf4dXvSsVoB4U66Yf2vLpruuNeYNA@mail.gmail.com>
Date:	Fri, 9 Jan 2015 11:24:10 -0800
From:	Yogesh Ahire <yogesh02061983@...il.com>
To:	Mike Galbraith <umgwanakikbuti@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: sched_yield() call on Linux Kernel 2.6.39 is not behaving correct

Thank you Mike. I didn't get what you mean by saying "its gona try to
yield for one hell of a long time before it succeeds".

On Thu, Jan 8, 2015 at 7:14 PM, Mike Galbraith <umgwanakikbuti@...il.com> wrote:
> On Thu, 2015-01-08 at 10:00 -0500, Yogesh Ahire wrote:
>> Thank you Mike. But I can see there are tasks with same priority and
>> are runnable waiting for CPU, following is the output of
>> /proc/sched_debug where you can see that the task "symphonyapp"
>> continuously calls sched_yield() but there are other tasks which are
>> ready to run are not getting CPU and are queued back.
>
> Something terminally bad happened.  With that tasks vruntime (tree-key),
> it's gonna try to yield for one hell of a long time before it succeeds.
>
> -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/