diff options
author | Joonsoo Kim <[email protected]> | 2016-05-05 16:22:35 -0700 |
---|---|---|
committer | Linus Torvalds <[email protected]> | 2016-05-05 17:38:53 -0700 |
commit | 7c31190bcfdbff225950902a9f226e4eb79ca94f (patch) | |
tree | 3d9c55c6df3e04a3c0a87106d4d424e8db1bcdb9 /tools/perf/util/trace-event-scripting.c | |
parent | 172400c69cb0d0d684b7cd75ac75872b3d7c61a1 (diff) |
lib/stackdepot: avoid to return 0 handle
Recently, we allow to save the stacktrace whose hashed value is 0. It
causes the problem that stackdepot could return 0 even if in success.
User of stackdepot cannot distinguish whether it is success or not so we
need to solve this problem. In this patch, 1 bit are added to handle
and make valid handle none 0 by setting this bit. After that, valid
handle will not be 0 and 0 handle will represent failure correctly.
Fixes: 33334e25769c ("lib/stackdepot.c: allow the stack trace hash to be zero")
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Joonsoo Kim <[email protected]>
Cc: Alexander Potapenko <[email protected]>
Cc: Andrey Ryabinin <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/util/trace-event-scripting.c')
0 files changed, 0 insertions, 0 deletions