diff options
| author | Darren Hart <dvhltc@us.ibm.com> | 2009-04-03 13:40:22 -0700 |
|---|---|---|
| committer | Thomas Gleixner <tglx@linutronix.de> | 2009-04-06 11:14:02 +0200 |
| commit | a72188d8a64ebe74722f1cf7ffac41b41ffdba21 (patch) | |
| tree | 5283404345b270bf5ca95ce8d792baacdf8cf7dc /mm | |
| parent | 8dac456a681bd94272ff50ecb31be6b669382c2b (diff) | |
| download | op-kernel-dev-a72188d8a64ebe74722f1cf7ffac41b41ffdba21.zip op-kernel-dev-a72188d8a64ebe74722f1cf7ffac41b41ffdba21.tar.gz | |
futex: add FUTEX_HAS_TIMEOUT flag to restart.futex.flags
Currently restart is only used if there is a timeout. The requeue_pi
functionality requires restarting to futex_lock_pi() on signal after
wakeup in futex_wait_requeue_pi() regardless of if there was a timeout
or not. Using 0 for the timeout value is confusing as that could
indicate an expired timer. The flag makes this explicit. While the
check is not technically needed in futex_wait_restart(), doing so
makes the code consistent with and will avoid confusion should the
need arise to restart wait without a timeout.
Signed-off-by: Darren Hart <dvhltc@us.ibm.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions
