linux-kernel - Re: [PATCH tip/master v4] kprobes: extable: Identify kprobes' insn-slots as kernel text area

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170110214207.dd52me5mtz6hhuzb@treble>
Date:   Tue, 10 Jan 2017 15:42:07 -0600
From:   Josh Poimboeuf <jpoimboe@...hat.com>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     Masami Hiramatsu <mhiramat@...nel.org>,
        Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
        Ananth N Mavinakayanahalli <ananth@...ux.vnet.ibm.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        "H . Peter Anvin" <hpa@...or.com>,
        Andrey Konovalov <andreyknvl@...gle.com>,
        Andy Lutomirski <luto@...nel.org>
Subject: Re: [PATCH tip/master v4] kprobes: extable: Identify kprobes'
 insn-slots as kernel text area

On Tue, Jan 10, 2017 at 09:59:23AM +0100, Peter Zijlstra wrote:
> On Mon, Jan 09, 2017 at 11:36:48AM -0600, Josh Poimboeuf wrote:
> > BTW, I think we'll have more problems with generated code if/when we
> > move to an x86 DWARF unwinder, because it won't have any idea how to
> > unwind past generated code.  Long term I wonder if it would make sense
> > to create some kind of framework for creating or registering generated
> > code, so we can solve these types of problems in a single place.
> 
> Yes, this seems like a good idea. Maybe we could pull the rbtree thing
> from modules and make that a more generic interface for code
> registration.

Yeah, a generic fast lookup for module+generated code could be useful.
It would also be nice to associate names with generated functions and
integrate that with kallsyms.  For DWARF we would also need a way to
associate CFI metadata with address ranges.

-- 
Josh