From: Steven Rostedt <rostedt@goodmis.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Hans de Goede <hdegoede@redhat.com>,
ksummit@lists.linux.dev
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] How far to go with eBPF
Date: Thu, 23 Jun 2022 17:36:54 -0400 [thread overview]
Message-ID: <20220623173654.4517e325@rorschach.local.home> (raw)
In-Reply-To: <CAADnVQ+4B3g9AwYp5zXXJ2c-G1L-aK69bqP8mztHGG2QgzwhaQ@mail.gmail.com>
On Thu, 23 Jun 2022 14:23:51 -0700
Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
> tracepoints exposed an api through cat-able and echo-able files
> that 'ubertrace' can use without any knowledge of the underlying kernel,
> without access to kernel sources, etc.
> Now please explain how bpf based tracing tools are similar?
> What exposed api do they use?
Question to you. Can eBPF provide information that normally is not
available without the eBPF program? Could there be someone that creates
a eBPF program based on internal information where that developer had
to read the kernel source to implement. But then provide this program
to other users that can now write programs based on that new
information?
Years and versions can go by, and the code that the eBPF program hasn't
changed so this works for years, without the maintainer of the attached
code even being aware of this use. Then one day that maintainer changes
the code and this eBPF program breaks for the first time in years, and
with that, it breaks all the user space applications that relied on
this.
I can see that change falling under the "broke user space" clause of
the Linux kernel and reverted.
next prev parent reply other threads:[~2022-06-23 21:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 6:55 [Ksummit-discuss] [MAINTAINERS SUMMIT] How far to go with eBPF Jiri Kosina
2022-06-15 8:05 ` Linus Walleij
2022-06-15 8:36 ` Jiri Kosina
2022-06-15 17:04 ` Jan Kara
2022-06-15 17:25 ` Jonathan Corbet
[not found] ` <20220615174601.GX1790663@paulmck-ThinkPad-P17-Gen-1>
2022-06-15 18:25 ` Jiri Kosina
2022-06-16 16:26 ` Steven Rostedt
2022-06-16 16:38 ` James Bottomley
2022-06-16 16:51 ` Steven Rostedt
2022-06-16 18:25 ` James Bottomley
2022-06-16 19:08 ` Steven Rostedt
2022-06-17 7:53 ` Jiri Kosina
2022-06-17 8:24 ` Linus Walleij
2022-06-17 10:30 ` Jan Kara
2022-06-17 11:04 ` Benjamin Tissoires
[not found] ` <dc6ca88d-d1ef-a1ab-dbef-e9338467271d@redhat.com>
2022-06-17 11:25 ` Benjamin Tissoires
2022-06-17 11:32 ` Hans de Goede
2022-06-20 13:13 ` Steven Rostedt
2022-06-21 15:05 ` Steven Rostedt
2022-06-21 16:33 ` Benjamin Tissoires
2022-06-23 20:15 ` Jiri Kosina
2022-06-23 21:23 ` Alexei Starovoitov
2022-06-23 21:36 ` Steven Rostedt [this message]
[not found] ` <20220615174358.GA26358@lst.de>
[not found] ` <CAO-hwJKqA07KX+6QtotCS8PtHFtk3DLQPJ3W8puaHOv7tOdi+Q@mail.gmail.com>
[not found] ` <20220616114856.GA11127@lst.de>
2022-06-16 12:14 ` Benjamin Tissoires
[not found] ` <CAO-hwJJmW_STS=nT22n4pcaZf9gz953K4o2vhgmq-ig4OzxOLg@mail.gmail.com>
2022-06-16 8:02 ` Jiri Kosina
2022-06-16 11:37 ` Linus Walleij
2022-06-16 12:09 ` Benjamin Tissoires
2022-06-15 18:35 ` Luis Chamberlain
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=20220623173654.4517e325@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=alexei.starovoitov@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=hdegoede@redhat.com \
--cc=jikos@kernel.org \
--cc=ksummit@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).