| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <582D445F.1050100@jp.fujitsu.com> Date: Thu, 17 Nov 2016 14:47:11 +0900 From: Masayoshi Mizuma <m.mizuma@...fujitsu.com> To: <linux-kernel@...r.kernel.org> CC: <m.mizuma@...fujitsu.com> Subject: [PATCH] list_debug: show address of prev and next when list_del corruption is detected. When list_del corruption is detected, the corruption may happen because of the region of prev or next is destroyed. So, the address of prev/next is useful to find the destroyer. Signed-off-by: Masayoshi Mizuma <m.mizuma@...fujitsu.com> --- lib/list_debug.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/lib/list_debug.c b/lib/list_debug.c index 3859bf6..a9cbcdb 100644 --- a/lib/list_debug.c +++ b/lib/list_debug.c @@ -55,11 +55,11 @@ void __list_del_entry(struct list_head *entry) "list_del corruption, %p->prev is LIST_POISON2 (%p)\n", entry, LIST_POISON2) || WARN(prev->next != entry, - "list_del corruption. prev->next should be %p, " - "but was %p\n", entry, prev->next) || + "list_del corruption. prev->next should be %p, but was %p (prev=%p)\n", + entry, prev->next, prev) || WARN(next->prev != entry, - "list_del corruption. next->prev should be %p, " - "but was %p\n", entry, next->prev)) + "list_del corruption. next->prev should be %p, but was %p (next=%p)\n", + entry, next->prev, next)) return; __list_del(prev, next); -- 1.8.3.1
Powered by blists - more mailing lists