netdev - Re: [oss-drivers] [PATCH bpf-next] tools: bpftool: warn about risky prog array updates

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: <b5ad02aa-f521-29bf-56e1-fc3520b94b98@netronome.com>
Date:   Mon, 28 Jan 2019 18:54:23 +0000
From:   Quentin Monnet <quentin.monnet@...ronome.com>
To:     Jakub Kicinski <jakub.kicinski@...ronome.com>
Cc:     Alexei Starovoitov <alexei.starovoitov@...il.com>,
        Daniel Borkmann <daniel@...earbox.net>,
        OSS-drivers Netronome <oss-drivers@...ronome.com>,
        Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: [oss-drivers] [PATCH bpf-next] tools: bpftool: warn about risky
 prog array updates

2019-01-28 18:51 UTC+0000 ~ Quentin Monnet <quentin.monnet@...ronome.com>
> On Mon, 28 Jan 2019 at 18:29, Jakub Kicinski
> <jakub.kicinski@...ronome.com> wrote:
>>
>> When prog array is updated with bpftool users often refer
>> to the map via the ID.  Unfortunately, that's likely
>> to lead to confusion because prog arrays get flushed when
>> the last user reference is gone.  If there is no other
>> reference bpftool will create one, update successfully
>> just to close the map again and have it flushed.
>>
>> Warn about this case in non-JSON mode.
>>
>> If the problem continues causing confusion we can remove
>> the support for referring to a map by ID for prog array
>> update completely.  For now it seems like the potential
>> inconvenience to users who know what they're doing outweighs
>> the benefit.
>>
>> Signed-off-by: Jakub Kicinski <jakub.kicinski@...ronome.com>
>> Reviewed-by: Quentin Monnet <quentin.monnet@...ronome.com>
> 
> All good for me!
> Quentin
> 

[Hmm. I read that on GMail interface and thought it was a repost on our 
internal ML. Sorry for the noise.]