[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131120153801.GA9743@gmail.com>
Date: Wed, 20 Nov 2013 16:38:01 +0100
From: Ingo Molnar <mingo@...nel.org>
To: "Frank Ch. Eigler" <fche@...hat.com>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
linux-arch@...r.kernel.org,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Sandeepa Prabhu <sandeepa.prabhu@...aro.org>, x86@...nel.org,
lkml <linux-kernel@...r.kernel.org>,
"Steven Rostedt (Red Hat)" <rostedt@...dmis.org>,
virtualization@...ts.linux-foundation.org,
systemtap@...rceware.org, "David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH -tip v3 00/23] kprobes: introduce NOKPROBE_SYMBOL() and
general cleaning of kprobe blacklist
* Frank Ch. Eigler <fche@...hat.com> wrote:
> masami.hiramatsu.pt wrote:
>
> > [...] This series also includes a change which prohibits probing
> > on the address in .entry.text because the code is used for very
> > low-level sensitive interrupt/syscall entries. Probing such code
> > may cause unexpected result (actually most of that area is already
> > in the kprobe blacklist). So I've decide to prohibit probing all
> > of them. [...]
>
> Does this new blacklist cover enough that the kernel now survives a
> broadly wildcarded perf-probe, e.g. over e.g. all of its kallsyms?
That's generally the purpose of the annotations - if it doesn't then
that's a bug.
Thanks,
Ingo
--
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