[lkml]   [2021]   [Jul]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] tracepoint: Add tracepoint_probe_register_may_exist() for BPF tracing
On Wed, Jul 7, 2021 at 5:05 PM Steven Rostedt <> wrote:
> On Wed, 7 Jul 2021 16:49:26 -0700
> Andrii Nakryiko <> wrote:
> > As for why the user might need that, it's up to the user and I don't
> > want to speculate because it will always sound contrived without a
> > specific production use case. But people are very creative and we try
> > not to dictate how and what can be done if it doesn't break any
> > fundamental assumption and safety.
> I guess it doesn't matter, because if they try to do it, the second
> attachment will simply fail to attach.

But not for the kprobe case.

And it might not always be possible to know that the same BPF program
is being attached. It could be attached by different processes that
re-use pinned program (without being aware of each other). Or it could
be done from some generic library that just accepts prog_fd and
doesn't really know the exact BPF program and whether it was already

Not sure why it doesn't matter that attachment will fail where it is
expected to succeed. The question is rather why such restriction?

> -- Steve

 \ /
  Last update: 2021-07-08 02:26    [W:0.072 / U:0.688 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site