On 1/24/22 9:15 AM, Andrii Nakryiko wrote:
> On Fri, Jan 21, 2022 at 12:43 PM Toke Høiland-Jørgensen <toke@xxxxxxxxxx> wrote:
>>
>> Andrii Nakryiko <andrii.nakryiko@xxxxxxxxx> writes:
>>
>>> On Thu, Jan 20, 2022 at 3:44 AM Toke Høiland-Jørgensen <toke@xxxxxxxxxx> wrote:
>>>>
>>>> Andrii Nakryiko <andrii@xxxxxxxxxx> writes:
>>>>
>>>>> Enact deprecation of legacy BPF map definition in SEC("maps") ([0]). For
>>>>> the definitions themselves introduce LIBBPF_STRICT_MAP_DEFINITIONS flag
>>>>> for libbpf strict mode. If it is set, error out on any struct
>>>>> bpf_map_def-based map definition. If not set, libbpf will print out
>>>>> a warning for each legacy BPF map to raise awareness that it goes
>>>>> away.
>>>>
>>>> We've touched upon this subject before, but I (still) don't think it's a
>>>> good idea to remove this support entirely: It makes it impossible to
>>>> write a loader that can handle both new and old BPF objects.
>>>>
>>>> So discourage the use of the old map definitions, sure, but please don't
>>>> make it completely impossible to load such objects.
>>>
>>> BTF-defined maps have been around for quite a long time now and only
>>> have benefits on top of the bpf_map_def way. The source code
>>> translation is also very straightforward. If someone didn't get around
>>> to update their BPF program in 2 years, I don't think we can do much
>>> about that.
>>>
>>> Maybe instead of trying to please everyone (especially those that
>>> refuse to do anything to their BPF programs), let's work together to
>>> nudge laggards to actually modernize their source code a little bit
>>> and gain some benefits from that along the way?
>>
>> I'm completely fine with nudging people towards the newer features, and
>> I think the compile-time deprecation warning when someone is using the
>> old-style map definitions in their BPF programs is an excellent way to
>> do that.
>>
>> I'm also fine with libbpf *by default* refusing to load programs that
>> use the old-style map definitions, but if the code is removed completely
>> it becomes impossible to write general-purpose loaders that can handle
>> both old and new programs. The obvious example of such a loader is
>> iproute2, the loader in xdp-tools is another.
>
> This is because you want to deviate from underlying BPF loader's
> behavior and feature set and dictate your own extended feature set in
> xdp-tools/iproute2/etc. You can technically do that, but with a lot of
> added complexity and headaches. But demanding libbpf to maintain
> deprecated and discouraged features/APIs/practices for 10+ years and
> accumulate all the internal cruft and maintenance burden isn't a great
> solution either.
>
> As of right now, recent 0.x libbpf versions do support "old and new
> programs", so there is always that option.
>
>>
>>> It's the same thinking with stricter section names, and all the other
>>> backwards incompatible changes that libbpf 1.0 will do.
>>
>> If the plan is to refuse entirely to load programs that use the older
>> section names, then I obviously have the same objection to that idea :)
>
> I understand, but I disagree about keeping them in libbpf
> indefinitely. That's why we have a major version bump at which point
> backwards compatibility isn't guaranteed. And we did a lot to make
> this transition smoother (all the libbpf_set_strict_mode()
> shenanigans) and prepare to it (it's been almost a year now (!), and
> we still have few more months).
>
>>
>>> If you absolutely cannot afford to drop support for all the
>>> to-be-removed things from libbpf, you'll have to stick to 0.x libbpf
>>> version. I assume (it will be up to disto maintainers, I suppose)
>>> you'll have that option.
>>
>> As in, you expect distributions to package up the old libbpf in a
>> separate package? Really?
>
> NixOS indicated that they are planning to do just that ([0]). Is it a
> problem to keep packaging libbpf.so.0 and libbpf.so.1 together?
>
> [0] https://github.com/libbpf/libbpf/issues/440#issuecomment-1016084088
>
>>
>> But either way, that doesn't really help; it just makes it a choice
>> between supporting new or old programs. Can't very well link to two
>> versions of the same library...
>
> Oh, you probably can with dynamic shared library loading, but yeah,
> big PITA for sure. But again, v0.x libbpf supports "new programs" for
> current definition of new, if you absolutely insist on supporting
> deprecated BPF object file features. I'd be happy if you could instead
> nudge your users to modernize their BPF game and prepare for libbpf
> 1.0 early, though. They can do that easily do to the extra work that
> we did for libbpf 1.0 transition period.
>
>>
>> I really don't get why you're so insistent on removing that code either;
>> it's not like it's code that has a lot of churn (by definition), nor is
>> it very much code in the first place. But if it's a question of
>
> There is enough and it is a maintenance burden. And will be forever if
> we don't take this chance to shed it and move everyone to better
> designed approaches (BTF-based maps), which, BTW, were around for
> about 2 years now. Hardly a novelty.
>
And it does not work everywhere.
When support for libbpf was added to iproute2, my biggest concern was
the stability of the library -- that exported APIs and supported
features would be arbitrarily changed and that is exactly what you are
doing with this push to v1.0. iproute2 cares about forward and backward
compatibility. If a tc program loads and runs on kernel version X with
iproute2 version Y, it should continue to work with kernel version X+M
and iproute2 version Y+N. No change should be required to the program at
all.
In this specific example, you are not removing support for old map
definitions for security reasons or bug reasons; you want to remove it
because there is a new definition and removing support for the older
definition forces people to move to the new style. You are trying to
force people to use a feature they may not care about at all or even need.
Ubuntu 18.04 is an LTS and will be around for a long time. ebpf programs
build and work just fine but the OS does not support BTF. Deprecating
support for older maps means people using say 18.04 and 22.04 can not
use the same object files on both servers which means code bases have to
deal with differences in definitions and build rules. Not user friendly
at all.
glibc manages to retain support for old system calls even as new
variants are added. That is part of the burden a library takes on for
its users. Your forced deprecation in short time windows (and 2 years is
a very short time window for OS'es) is just going to cause headaches -
like splits where code bases have to jump through hoops to stay on pre-1.0.
