From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: ast@kernel.org, netdev@vger.kernel.org
Subject: Re: pull-request: bpf-next 2018-01-11
Date: Thu, 11 Jan 2018 14:00:05 -0500 (EST) [thread overview]
Message-ID: <20180111.140005.1020010084255071788.davem@davemloft.net> (raw)
In-Reply-To: <20180111021313.3116-1-daniel@iogearbox.net>
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.
prev parent reply other threads:[~2018-01-11 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 2:13 pull-request: bpf-next 2018-01-11 Daniel Borkmann
2018-01-11 19:00 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180111.140005.1020010084255071788.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).