From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: pull-request: bpf-next 2018-01-11
Date: Thu, 11 Jan 2018 14:00:05 -0500 (EST)
Message-ID: <20180111.140005.1020010084255071788.davem@davemloft.net>
References: <20180111021313.3116-1-daniel@iogearbox.net>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: ast@kernel.org, netdev@vger.kernel.org
To: daniel@iogearbox.net
Return-path: <netdev-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([184.105.139.130]:41612 "EHLO
        shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S933141AbeAKTAG (ORCPT
        <rfc822;netdev@vger.kernel.org>); Thu, 11 Jan 2018 14:00:06 -0500
In-Reply-To: <20180111021313.3116-1-daniel@iogearbox.net>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

From: Daniel Borkmann <daniel@iogearbox.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.