summaryrefslogtreecommitdiffstats
path: root/net/ieee802154/nl_policy.c
diff options
context:
space:
mode:
authorMarco Elver <elver@google.com>2019-07-11 20:53:49 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2019-07-12 11:05:42 -0700
commite89692190065c12386bd37272ae8b7d142dd079f (patch)
tree0556f4730cc25ad36637c4b9051607c3f6ad5e22 /net/ieee802154/nl_policy.c
parentb7c3613e685076bad6e5540501d84cc31bb30377 (diff)
downloadlinux-e89692190065c12386bd37272ae8b7d142dd079f.tar.gz
linux-e89692190065c12386bd37272ae8b7d142dd079f.tar.bz2
linux-e89692190065c12386bd37272ae8b7d142dd079f.zip
mm/kasan: print frame description for stack bugs
This adds support for printing stack frame description on invalid stack accesses. The frame description is embedded by the compiler, which is parsed and then pretty-printed. Currently, we can only print the stack frame info for accesses to the task's own stack, but not accesses to other tasks' stacks. Example of what it looks like: page dumped because: kasan: bad access detected addr ffff8880673ef98a is located in stack of task insmod/2008 at offset 106 in frame: kasan_stack_oob+0x0/0xf5 [test_kasan] this frame has 2 objects: [32, 36) 'i' [96, 106) 'stack_array' Memory state around the buggy address: Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=198435 Link: http://lkml.kernel.org/r/20190522100048.146841-1-elver@google.com Signed-off-by: Marco Elver <elver@google.com> Reviewed-by: Andrey Ryabinin <aryabinin@virtuozzo.com> Cc: Alexander Potapenko <glider@google.com> Cc: Dmitry Vyukov <dvyukov@google.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'net/ieee802154/nl_policy.c')
0 files changed, 0 insertions, 0 deletions