debugobjects: Make stack check warning more informative
authorJoel Fernandes (Google) <joel@joelfernandes.org>
Mon, 23 Jul 2018 21:25:31 +0000 (14:25 -0700)
committerThomas Gleixner <tglx@linutronix.de>
Mon, 30 Jul 2018 19:36:37 +0000 (21:36 +0200)
commitfc91a3c4c27acdca0bc13af6fbb68c35cfd519f2
tree09d795cb9edc99c1b81a427ec8310046f1d0268d
parentacb1872577b346bd15ab3a3f8dff780d6cca4b70
debugobjects: Make stack check warning more informative

While debugging an issue debugobject tracking warned about an annotation
issue of an object on stack. It turned out that the issue was due to the
object in concern being on a different stack which was due to another
issue.

Thomas suggested to print the pointers and the location of the stack for
the currently running task. This helped to figure out that the object was
on the wrong stack.

As this is general useful information for debugging similar issues, make
the error message more informative by printing the pointers.

[ tglx: Massaged changelog ]

Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Waiman Long <longman@redhat.com>
Acked-by: Yang Shi <yang.shi@linux.alibaba.com>
Cc: kernel-team@android.com
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: astrachan@google.com
Link: https://lkml.kernel.org/r/20180723212531.202328-1-joel@joelfernandes.org
lib/debugobjects.c