Messages in this thread |  | | | Subject | Re: [RT] bad BUG_ON in rtmutex.c | | From | Steven Rostedt <> | | Date | Tue, 18 Apr 2006 09:55:32 -0400 |
| |
On Tue, 2006-04-18 at 09:50 -0400, Steven Rostedt wrote:
> BUT! I need to take another good look at the code, and maybe my > previous example of the failed BUG_ON is really a clue that there exists > a deeper bug. If the processes D and E from my last example were of > different priorities, but still higher than A, could the end result be > setting A to the lower of the two? This would be a bug, because then A > would not inherit the correct priority!
OK, this shouldn't be a problem (answering my own question ;).
The setting of the task's prio is done by __rt_mutex_adjust_prio(task) and this sets the task's prio to the highest prio task that is blocked on a lock own by "task", or to "task"s original prio if that is higher.
So nevermind.
-- Steve
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |