From: Steven Rostedt <rostedt@goodmis.org>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
syzbot+721aa903751db87aa244@syzkaller.appspotmail.com,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Ingo Molnar <mingo@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
netdev <netdev@vger.kernel.org>, bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH] tracepoint: Add tracepoint_probe_register_may_exist() for BPF tracing
Date: Wed, 7 Jul 2021 20:05:44 -0400 [thread overview]
Message-ID: <20210707200544.1fbfd42b@rorschach.local.home> (raw)
In-Reply-To: <CAEf4BzZ=hFZw1RNx0Pw=kMNq2xRrqHYCQQ_TY_pt86Zg9HFJfA@mail.gmail.com>
On Wed, 7 Jul 2021 16:49:26 -0700
Andrii Nakryiko <andrii.nakryiko@gmail.com> 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.
-- Steve
next prev parent reply other threads:[~2021-07-08 0:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 13:55 [PATCH] tracepoint: Add tracepoint_probe_register_may_exist() for BPF tracing Steven Rostedt
2021-06-29 14:16 ` [syzbot] WARNING in tracepoint_add_func syzbot
2021-07-07 22:12 ` [PATCH] tracepoint: Add tracepoint_probe_register_may_exist() for BPF tracing Andrii Nakryiko
2021-07-07 22:45 ` Steven Rostedt
2021-07-07 23:49 ` Andrii Nakryiko
2021-07-08 0:05 ` Steven Rostedt [this message]
2021-07-08 0:23 ` Andrii Nakryiko
2021-07-08 0:43 ` Steven Rostedt
2021-07-08 20:04 ` Andrii Nakryiko
2021-07-08 17:30 ` Mathieu Desnoyers
2021-07-08 20:11 ` Andrii Nakryiko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210707200544.1fbfd42b@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=syzbot+721aa903751db87aa244@syzkaller.appspotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).