On Thu, 3 Feb 2022 17:34:54 -0800 Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx> wrote: > On Thu, Feb 3, 2022 at 4:46 PM Masami Hiramatsu <mhiramat@xxxxxxxxxx> wrote: > > > > I thought What Alexei pointed was that don't expose the FPROBE name > > to user space. If so, I agree with that. We can continue to use > > KPROBE for user space. Using fprobe is just for kernel implementation. > > Clearly that intent is not working. Thanks for confirmation :-) > The "fprobe" name is already leaking outside of the kernel internals. > The module interface is being proposed. Yes, but that is only for making the example module. It is easy for me to enclose it inside kernel. I'm preparing KUnit selftest code for next version. After integrated that, we don't need that example module anymore. > You'd need to document it, etc. Yes, I've added a document of the APIs for the series. :-) > I think it's only causing confusion to users. > The new name serves no additional purpose other than > being new and unheard of. > fprobe is kprobe on ftrace. That's it. No, fprobe is NOT kprobe on ftrace, kprobe on ftrace is already implemented transparently. > Just call it kprobe on ftrace in api and everywhere. > Please? Hmm, no, I think that's the work for who provide user-interface, isn't it?. Inside kernel, IMHO, the interface named from the programing viewpoint, and from that viewpoint, fprobe and kprobe interface are similar but different. I'm able to allow kprobe-event (of ftrace) to accept "func*" (yeah, that's actually good idea), but ftrace interface will not export as fprobe. Even if it internally uses fprobe, I don't call it fprobe. It's kprobes from the viewpoint of ftrace user. (Yeah, I think it should be called as "dynamic-probe-event-for-kernel" but historically, it is called as kprobe-event.) Thank you, -- Masami Hiramatsu <mhiramat@xxxxxxxxxx>
