lkml.org 
[lkml]   [2022]   [Jun]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] kprobes: Enable tracing for mololithic kernel images
    On Tue, Jun 14, 2022 at 03:32:38PM +0300, jarkko@kernel.org wrote:
    > > Like say for a next step we moved prog pack out of bpf into core code,
    > > gave it it's own copy of module_alloc(), and then made kprobes use it.
    > > Then we would have something with improved W^X guard rails, and kprobes
    > > would not depend on modules anymore. I think maybe it's a step in the
    > > right direction, even if it's not perfect.
    >
    > So you're saying that I should (as a first step) basically clone
    > module_alloc() implementation for kprobes, and future for BPF
    > use, in order to get a clean starting point?

    I don't think cloning the code helps anyone. The fact that except
    for the eBPF mess everyone uses module_alloc and the related
    infrastructure is a feature and not a bug. The interface should
    become better than what we have right now, but there is few enough
    users that this can be done in one go.

    So assuming we really care deeply enough about fancy tracing without
    modules (and I'm not sure we do, even if you don't use modules it
    doesn't hurt to just build the modules code, I do that all the time
    for my test machines), the general approach in your series is the
    right one.

    \
     
     \ /
      Last update: 2022-06-15 08:37    [W:2.179 / U:0.284 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site