netdev - Re: [PATCH net-next v2 0/2] libbpf: support more map options

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: <20171003.212645.898173960092356152.davem@davemloft.net>
Date:   Tue, 03 Oct 2017 21:26:45 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     kraigatgoog@...il.com
Cc:     ast@...com, daniel@...earbox.net, brouer@...hat.com,
        chonggangli@...gle.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2 0/2] libbpf: support more map options

From: Craig Gallek <kraigatgoog@...il.com>
Date: Mon,  2 Oct 2017 12:41:27 -0400

> From: Craig Gallek <kraig@...gle.com>
> 
> The functional change to this series is the ability to use flags when
> creating maps from object files loaded by libbpf.  In order to do this,
> the first patch updates the library to handle map definitions that
> differ in size from libbpf's struct bpf_map_def.
> 
> For object files with a larger map definition, libbpf will continue to load
> if the unknown fields are all zero, otherwise the map is rejected.  If the
> map definition in the object file is smaller than expected, libbpf will use
> zero as a default value in the missing fields.

Judging by the feedback I anticipate another spin of this series.