[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e9e81427-c0d7-4a1e-ba9b-c51fd3c683ac@solarflare.com>
Date: Wed, 1 Apr 2020 15:26:04 +0100
From: Edward Cree <ecree@...arflare.com>
To: Andrii Nakryiko <andrii.nakryiko@...il.com>
CC: David Ahern <dsahern@...il.com>,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
Andrii Nakryiko <andriin@...com>, bpf <bpf@...r.kernel.org>,
Networking <netdev@...r.kernel.org>,
"Alexei Starovoitov" <ast@...com>,
Daniel Borkmann <daniel@...earbox.net>,
"Andrey Ignatov" <rdna@...com>, Kernel Team <kernel-team@...com>
Subject: Re: [PATCH v3 bpf-next 0/4] Add support for cgroup bpf_link
On 01/04/2020 01:22, Andrii Nakryiko wrote:
> Can you please point out where I was objecting to observability API
> (which is LINK_QUERY thing we've discussed and I didn't oppose, and
> I'm going to add next)?
I didn't say you objected to it.
I just said that you argued that it was OK for it to not land in the
same release as the rest of the API, because drgn could paper over
that gap. Which seems to me to signify a dangerous way of thinking,
and I wanted to raise the alarm about that.
(If you _don't_ see what's wrong with that argument... well, that'd
be even _more_ alarming. Debuggers — and fuser, for that matter —
are for when things go wrong _in ways the designers of the system
failed to anticipate_. They should not be part of a 'normal' work-
flow for dealing with problems that we already _know_ are possible;
it's kinda-sorta like how exceptions shouldn't be used for non-
exceptional situations.)
-ed
Powered by blists - more mailing lists