* Esben Nielsen <[email protected]> wrote:
> > Now the question is, who will fix it? Preferably the maintainers, but I
> > don't know how much of a priority this is to them. I don't have the time
> > now to look at this and understand enough about the code to be able to
> > make a proper fix, and I'm sure you have other things to do too.
>
> How about adding a
> if(rt_task(current)) {
> WARN_ON(1);
> mutex_setprio(current, MAX_PRIO-1)
> }
> ?
>
> to find all calls to yields from rt-tasks. That will force the user
> (aka the real-time developer) to either stop calling the subsystems
> still using yield from his RT-tasks, or fix those subsystems.
i've added this to the -43-08 patch, so that we can see the scope of the
problem. But any yield() use could become a problem due to priority
inheritance. (which might eventually be expanded to userspace locking
too)
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
