[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPDLWs8tJ5voge-gS-W+gxpRRk2GximPkGm1d9pxf5QNbCKufA@mail.gmail.com>
Date: Tue, 28 Nov 2017 08:58:44 +0530
From: Kaiwan N Billimoria <kaiwan@...wantech.com>
To: "Tobin C. Harding" <me@...in.cc>
Cc: Kees Cook <keescook@...omium.org>, kernel-hardening@...ts.openwall.com,
LKML <linux-kernel@...r.kernel.org>, Network Development <netdev@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>, Tycho Andersen <tycho@...ho.ws>
Subject: Re: Re: [RFC 0/3] kallsyms: don't leak address
when printing symbol
On Tue, Nov 28, 2017 at 7:20 AM, Tobin C. Harding <me@...in.cc> wrote:
>
> Noob question: how do we _know_ this. In other words how do we know no
> userland tools rely on the current behaviour? No stress to answer Kees,
> this is a pretty general kernel dev question.
Perhaps I'm reading this wrong, but anyway: besides ftrace, kprobes
will require a
symbol-to-address lookup. Specifically, in the function
kprobe_lookup_name() which
in turn invokes kallsyms_lookup_name().
AFAIK, SystemTap (userland) is built on top of the kprobes infrastructure..
thanks,
Kaiwan.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
