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
| ||
|
Date: Fri, 24 Sep 2010 20:04:17 +0200 From: Jiri Olsa <jolsa@...hat.com> To: jason.wessel@...driver.com, a.p.zijlstra@...llo.nl Cc: kgdb-bugreport@...ts.sourceforge.net, linux-kernel@...r.kernel.org Subject: kgdb segv in the latest tip due to perf ctx changes hi, while starting kgdb early debug on latest tip tree, I got SIGSEGV inside kernel in following location: fetch_bp_busy_slots (bp=0xffff880075f69000) at kernel/hw_breakpoint.c:137 137 struct task_struct *tsk = bp->ctx->task; the segv is caused by the kgdb code assuming the event has ctx field defined, which is not true at the the time by the following backtrace: (gdb) bt #0 fetch_bp_busy_slots (bp=0xffff880075f69000) at kernel/hw_breakpoint.c:137 #1 __reserve_bp_slot (bp=0xffff880075f69000) at kernel/hw_breakpoint.c:314 #2 0xffffffff810ac0c5 in reserve_bp_slot (bp=0xffff880075f69000) at kernel/hw_breakpoint.c:336 #3 0xffffffff810ac0f6 in register_perf_hw_breakpoint (bp=0xffff880075f69000) at kernel/hw_breakpoint.c:412 #4 0xffffffff810ac165 in hw_breakpoint_event_init (bp=0xffff880075f69000) at kernel/hw_breakpoint.c:580 #5 0xffffffff810a3da6 in perf_init_event (event=0xffff880075f69000) at kernel/perf_event.c:5268 #6 0xffffffff810aa658 in perf_event_alloc (attr=0xffff88007899ddf0, cpu=0, group_leader=0xffff880075f69000, parent_event=0x0, overflow_handler=0) at kernel/perf_event.c:5356 #7 0xffffffff810aae6c in perf_event_create_kernel_counter (attr=<value optimized out>, cpu=0, task=0x0, overflow_handler=<value optimized out>) at kernel/perf_event.c:5752 #8 0xffffffff810ab8b5 in register_wide_hw_breakpoint (attr=0xffff88007899ddf0, triggered=0) at kernel/hw_breakpoint.c:518 #9 0xffffffff81025e2a in kgdb_arch_late () at arch/x86/kernel/kgdb.c:646 #10 0xffffffff8107be62 in kgdb_register_callbacks (new_dbg_io_ops=0xffffffff81a3de00) at kernel/debug/debug_core.c:802 #11 kgdb_register_io_module (new_dbg_io_ops=0xffffffff81a3de00) at kernel/debug/debug_core.c:906 #12 0xffffffff812662bc in configure_kgdboc () at drivers/serial/kgdboc.c:137 #13 0xffffffff81ae805b in init_kgdboc () at drivers/serial/kgdboc.c:159 #14 0xffffffff81abd61e in do_one_initcall (fn=0xffffffff81ae8047 <init_kgdboc>) at init/main.c:750 #15 0xffffffff81abd828 in do_initcalls (unused=<value optimized out>) at init/main.c:780 #16 do_basic_setup (unused=<value optimized out>) at init/main.c:801 #17 kernel_init (unused=<value optimized out>) at init/main.c:893 #18 0xffffffff810033d4 in ?? () at arch/x86/kernel/entry_64.S:1156 #19 0x0000000000000000 in ?? () I found out it's due to foolowing commit, that's causing the init code to be called without the ctx field being defined... commit c3f00c70276d8ae82578c8b773e2db657f69a478 Author: Peter Zijlstra <a.p.zijlstra@...llo.nl> Date: Wed Aug 18 14:37:15 2010 +0200 I'm not sure if kgdb is wrong assuming the filed exists or perf code not defining the ctx field at that time.. I can reproduce easily, let me know if I can help wbr, jirka -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists