diff options
| author | Darren Hart <[email protected]> | 2011-04-14 15:41:57 -0700 |
|---|---|---|
| committer | Thomas Gleixner <[email protected]> | 2011-04-15 16:34:32 +0200 |
| commit | 0cd9c6494ee5c19aef085152bc37f3a4e774a9e1 (patch) | |
| tree | 5d24e41c96d4d80e92213520dd98d05695bc0c03 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | a6360dd37e1a144ed11e6548371bade559a1e4df (diff) | |
futex: Set FLAGS_HAS_TIMEOUT during futex_wait restart setup
The FLAGS_HAS_TIMEOUT flag was not getting set, causing the restart_block to
restart futex_wait() without a timeout after a signal.
Commit b41277dc7a18ee332d in 2.6.38 introduced the regression by accidentally
removing the the FLAGS_HAS_TIMEOUT assignment from futex_wait() during the setup
of the restart block. Restore the originaly behavior.
Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=32922
Reported-by: Tim Smith <[email protected]>
Reported-by: Torsten Hilbrich <[email protected]>
Signed-off-by: Darren Hart <[email protected]>
Signed-off-by: Eric Dumazet <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: John Kacur <[email protected]>
Cc: [email protected]
Link: http://lkml.kernel.org/r/%3Cdaac0eb3af607f72b9a4d3126b2ba8fb5ed3b883.1302820917.git.dvhart%40linux.intel.com%3E
Signed-off-by: Thomas Gleixner <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions