[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84li9ke88w.fsf@sauna.l.org>
Date: Mon, 18 Mar 2013 22:57:35 +0200
From: Timo Juhani Lindfors <timo.lindfors@....fi>
To: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Pavel Emelyanov <xemul@...allels.com>,
Jiri Kosina <jkosina@...e.cz>,
Nadia Yvette Chambers <nyc@...omorphy.com>,
yrl.pp-manager.tt@...achi.com,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH -tip ] [BUGFIX] kprobes: Move hash_64() into .text.kprobe section
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com> writes:
> Thank you for reporting!!
Thanks for fixing these! I spent some time trying to automate the
process of finding sensitive functions and eventually resorted into
booting a kvm instance with a minimal initrd to test every single
function in a clean and reproducible environment.
I found 7 more cases where calling register_kprobe() leads to an instant
kernel panic:
__flush_tlb_single
native_flush_tlb
native_safe_halt
native_set_pgd
native_set_pmd
native_set_pud
native_write_cr0
You can see full kernel console output for each function at
http://lindi.iki.fi/lindi/linux/kprobes/panics_2013-03-18/
--
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