diff options
author | 2016-05-05 16:22:35 -0700 | |
---|---|---|
committer | 2016-05-05 17:38:53 -0700 | |
commit | 7c31190bcfdbff225950902a9f226e4eb79ca94f (patch) | |
tree | 3d9c55c6df3e04a3c0a87106d4d424e8db1bcdb9 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | mm: fix kcompactd hang during memory offlining (diff) | |
download | wireguard-linux-7c31190bcfdbff225950902a9f226e4eb79ca94f.tar.xz wireguard-linux-7c31190bcfdbff225950902a9f226e4eb79ca94f.zip |
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/1462252403-1106-1-git-send-email-iamjoonsoo.kim@lge.com
Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Alexander Potapenko <glider@google.com>
Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions