[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131121072938.GA16912@gmail.com>
Date: Thu, 21 Nov 2013 08:29:38 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc: "Frank Ch. Eigler" <fche@...hat.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
* Masami Hiramatsu <masami.hiramatsu.pt@...achi.com> wrote:
> (2013/11/21 2:36), Frank Ch. Eigler wrote:
[ ... ]
> > one needs to resort to something like:
> >
> > # cat /proc/kallsyms | grep ' [tT] ' | while read addr type symbol; do
> > perf probe $symbol
> > done
> >
> > then wait for a few hours for that to finish. Then, or while the loop
> > is still running, run
> >
> > # perf record -e 'probe:*' -aR sleep 1
> >
> > to take a kernel down.
>
> Um, indeed, current blacklist is not perfect. [...]
Then it needs to be fixed ASAP!
> [...] As I reported in this series, I've found 2 more patterns. I
> guess there still have some others.
>
> But anyway, I don't think it is good to fix all such bugs in this
> series.
Fixing these bugs is far more important than any cleanup work.
We can apply the fixes together with your cleanup series to make it
all simpler, but the bug fixing absolutely needs to happen right now.
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