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. The "fprobe" name is already leaking outside of the kernel internals. The module interface is being proposed. You'd need to document it, etc. 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. Just call it kprobe on ftrace in api and everywhere. Please?
