summaryrefslogtreecommitdiffstats
path: root/init/Kconfig
diff options
context:
space:
mode:
authorSteven Rostedt <srostedt@redhat.com>2011-01-06 15:08:29 -0500
committerIngo Molnar <mingo@elte.hu>2011-01-11 15:17:24 +0100
commitf123c98e7f168e949b283690693695f988332c3d (patch)
tree18e3421ae3e23625686564af36ca844805cf812d /init/Kconfig
parentcb600d2f83c854ec3d6660063e4466431999489b (diff)
downloadop-kernel-dev-f123c98e7f168e949b283690693695f988332c3d.zip
op-kernel-dev-f123c98e7f168e949b283690693695f988332c3d.tar.gz
rtmutex: Fix comment about why new_owner can be NULL in wake_futex_pi()
The comment about why rt_mutex_next_owner() can return NULL in wake_futex_pi() is not the normal case. Tracing the cause of why this occurs is more likely that waiter simply timedout. But because it originally caused contention with the futex, the owner will go into the kernel when it unlocks the lock. Then it will hit this code path and rt_mutex_next_owner() will return NULL. Cc: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Steven Rostedt <rostedt@goodmis.org> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'init/Kconfig')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud