netdev - Re: [RFC bpf-next 00/10] initial control flow support for eBPF verifier

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: <20180508.202828.699453038949941467.davem@davemloft.net>
Date:   Tue, 08 May 2018 20:28:28 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     jiong.wang@...ronome.com
Cc:     alexei.starovoitov@...il.com, daniel@...earbox.net,
        john.fastabend@...il.com, netdev@...r.kernel.org,
        oss-drivers@...ronome.com
Subject: Re: [RFC bpf-next 00/10] initial control flow support for eBPF
 verifier

From: Jiong Wang <jiong.wang@...ronome.com>
Date: Mon,  7 May 2018 06:22:36 -0400

> This infrastructure comes with some memory usage and execution time cost.
> Memory pool based allocation is used to avoid frequently calling of
> kmalloc/free. Singly linked list and compact pointer are used to reduce
> various cfg node size.

The memory and execution time costs are unfortunate, but we will
certainly need a real control flow graph in the verifier whether we
like it or not.