diff options
| author | Marc Zyngier <[email protected]> | 2016-01-15 17:41:09 +0000 |
|---|---|---|
| committer | Thomas Gleixner <[email protected]> | 2017-02-18 10:58:39 +0100 |
| commit | 336a9cde10d641e70bac67d90ae91b3190c3edca (patch) | |
| tree | 6b987abecbe65d4ed1dcd3a9d5ad4e2215b4bac8 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | dba9a0babdd938a51d11ae81f9c40d07ca613f43 (diff) | |
hrtimer: Catch invalid clockids again
commit 82e88ff1ea94 ("hrtimer: Revert CLOCK_MONOTONIC_RAW support") removed
unfortunately a sanity check in the hrtimer code which was part of that
MONOTONIC_RAW patch series.
It would have caught the bogus usage of CLOCK_MONOTONIC_RAW in the wireless
code. So bring it back.
It is way too easy to take any random clockid and feed it to the hrtimer
subsystem. At best, it gets mapped to a monotonic base, but it would be
better to just catch illegal values as early as possible.
Detect invalid clockids, map them to CLOCK_MONOTONIC and emit a warning.
[ tglx: Replaced the BUG by a WARN and gracefully map to CLOCK_MONOTONIC ]
Signed-off-by: Marc Zyngier <[email protected]>
Cc: Tomasz Nowicki <[email protected]>
Cc: Christoffer Dall <[email protected]>
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Thomas Gleixner <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions