netdev - Re: pull-request: bpf-next 2018-01-11

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]

Date:   Thu, 11 Jan 2018 14:00:05 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     daniel@...earbox.net
Cc:     ast@...nel.org, netdev@...r.kernel.org
Subject: Re: pull-request: bpf-next 2018-01-11

From: Daniel Borkmann <daniel@...earbox.net>
Date: Thu, 11 Jan 2018 03:13:13 +0100

> The following pull-request contains BPF updates for your *net-next* tree.
> 
> The main changes are:
> 
> 1) Various BPF related improvements and fixes to nfp driver: i) do
>    not register XDP RXQ structure to control queues, ii) round up
>    program stack size to word size for nfp, iii) restrict MTU changes
>    when BPF offload is active, iv) add more fully featured relocation
>    support to JIT, v) add support for signed compare instructions to
>    the nfp JIT, vi) export and reuse verfier log routine for nfp, and
>    many more, from Jakub, Quentin and Nic.
> 
> 2) Fix a syzkaller reported GPF in BPF's copy_verifier_state() when
>    we hit kmalloc failure path, from Alexei.
> 
> 3) Add two follow-up fixes for the recent XDP RXQ series: i) kvzalloc()
>    allocated memory was only kfree()'ed, and ii) fix a memory leak where
>    RX queue was not freed in netif_free_rx_queues(), from Jakub.
> 
> 4) Add a sample for transferring XDP meta data into the skb, here it
>    is used for setting skb->mark with the buffer from XDP, from Jesper.
> 
> Please consider pulling these changes from:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git

Pulled, thanks Daniel.

> Note, getting bpf-next out earlier this time around in order to
> pull in dependencies from bpf that are needed in bpf-next for
> upcoming series such as maps offload.

Ok.