netdev - Re: [PATCH bpf v4 0/2] bpf: change uapi for bpf iterator map elements

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] [day] [month] [year] [list]

Message-ID: <CAADnVQJ0Q7R9K9orMkpRWZ3jKSMvTu+jD72Vd=GSXLyAftz3FQ@mail.gmail.com>
Date:   Thu, 6 Aug 2020 16:46:13 -0700
From:   Alexei Starovoitov <alexei.starovoitov@...il.com>
To:     Yonghong Song <yhs@...com>
Cc:     bpf <bpf@...r.kernel.org>,
        Network Development <netdev@...r.kernel.org>,
        Alexei Starovoitov <ast@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>,
        Kernel Team <kernel-team@...com>
Subject: Re: [PATCH bpf v4 0/2] bpf: change uapi for bpf iterator map elements

On Tue, Aug 4, 2020 at 10:51 PM Yonghong Song <yhs@...com> wrote:
>
> Andrii raised a concern that current uapi for bpf iterator map
> element is a little restrictive and not suitable for future potential
> complex customization. This is a valid suggestion, considering people
> may indeed add more complex custimization to the iterator, e.g.,
> cgroup_id + user_id, etc. for task or task_file. Another example might
> be map_id plus additional control so that the bpf iterator may bail
> out a bucket earlier if a bucket has too many elements which may hold
> lock too long and impact other parts of systems.
>
> Patch #1 modified uapi with kernel changes. Patch #2
> adjusted libbpf api accordingly.
>
> Changelogs:
>   v3 -> v4:
>     . add a forward declaration of bpf_iter_link_info in
>       tools/lib/bpf/bpf.h in case that libbpf is built against
>       not-latest uapi bpf.h.
>     . target the patch set to "bpf" instead of "bpf-next"

Applied. Thanks