| 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
| ||
|
Message-ID: <CAMJ=MEdNURgC-vmn-gTnGnBXQbMeMi8kvxCFyw4f2KnZTPCjeA@mail.gmail.com> Date: Thu, 7 May 2015 22:17:48 +0200 From: Ronny Meeus <ronny.meeus@...il.com> To: Steven Rostedt <rostedt@...dmis.org> Cc: Mike Galbraith <umgwanakikbuti@...il.com>, linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de> Subject: Re: Issue in PI boosting code in __sched_setscheduler On Wed, May 6, 2015 at 5:23 AM, Steven Rostedt <rostedt@...dmis.org> wrote: > On Wed, 6 May 2015 05:14:18 +0200 > Ronny Meeus <ronny.meeus@...il.com> wrote: > >> Thanks for looking into this. >> >> It looks to me that real-time priority threads are not used in many >> systems because we discovered already several issues, both in the >> kernel and glibc while we are using Linux only recently. >> Do you have a view on this? >> > > View on what? Whether the real-time priority threads are used a lot. I have the impression that there are severe issues in the Linux eco system (Kernel+glibc) when it comes to real-time priority handling. > Anyway, did you see the patch Thomas sent out? I did not see, I will have a look right away. > > Subject: [PATCH V2] sched: Handle priority boosted tasks proper in setscheduler() > > It solves this current issue. > > -- Steve -- 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/
Powered by blists - more mailing lists