netdev - Re: libbpf distro packaging

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a00bab9b-dae8-23d8-8de0-3751a1d1b023@fb.com>
Date:   Fri, 23 Aug 2019 16:00:01 +0000
From:   Alexei Starovoitov <ast@...com>
To:     Jiri Olsa <jolsa@...hat.com>, Julia Kartseva <hex@...com>
CC:     Andrii Nakryiko <andrii.nakryiko@...il.com>,
        "labbott@...hat.com" <labbott@...hat.com>,
        "acme@...nel.org" <acme@...nel.org>,
        "debian-kernel@...ts.debian.org" <debian-kernel@...ts.debian.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Andrey Ignatov <rdna@...com>, Yonghong Song <yhs@...com>,
        "jolsa@...nel.org" <jolsa@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>
Subject: Re: libbpf distro packaging

On 8/23/19 2:22 AM, Jiri Olsa wrote:
> btw, the libbpf GH repo tag v0.0.4 has 0.0.3 version set in Makefile:
> 
>    VERSION = 0
>    PATCHLEVEL = 0
>    EXTRAVERSION = 3
> 
> current code takes version from libbpf.map so it's fine,
> but would be great to start from 0.0.5 so we don't need to
> bother with rpm patches.. is 0.0.5 planned soon?

Technically we can bump it at any time.
The goal was to bump it only when new kernel is released
to capture a collection of new APIs in a given 0.0.X release.
So that libbpf versions are synchronized with kernel versions
in some what loose way.
In this case we can make an exception and bump it now.