netdev - Re: [PATCH bpf-next v5 0/2] bpf: allow map helpers access to map values directly

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: <1cfb972b-2a1e-8cdf-612f-014d2ad20d63@iogearbox.net>
Date:   Tue, 24 Apr 2018 23:54:32 +0200
From:   Daniel Borkmann <daniel@...earbox.net>
To:     Paul Chaignon <paul.chaignon@...nge.com>,
        Alexei Starovoitov <ast@...nel.org>, netdev@...r.kernel.org
Cc:     iovisor-dev@...ts.iovisor.org, paul.chaignon@...il.com
Subject: Re: [PATCH bpf-next v5 0/2] bpf: allow map helpers access to map
 values directly

On 04/24/2018 03:06 PM, Paul Chaignon wrote:
> Currently, helpers that expect ARG_PTR_TO_MAP_KEY and ARG_PTR_TO_MAP_VALUE
> can only access stack and packet memory.  This patchset allows these
> helpers to directly access map values by passing registers of type
> PTR_TO_MAP_VALUE.
> 
> The first patch changes the verifier; the second adds new test cases.
> 
> The first three versions of this patchset were sent on the iovisor-dev
> mailing list only.
> 
> Changelogs:
>   Changes in v5:
>     - Refactor using check_helper_mem_access.
>   Changes in v4:
>     - Rebase.
>   Changes in v3:
>     - Bug fixes.
>     - Negative test cases.
>   Changes in v2:
>     - Additional test cases for adjusted maps.

Applied to bpf-next, thanks Paul!