From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: ast@kernel.org, netdev@vger.kernel.org
Subject: Re: pull-request: bpf 2019-01-20
Date: Sat, 19 Jan 2019 16:44:36 -0800 (PST) [thread overview]
Message-ID: <20190119.164436.335693369841017747.davem@davemloft.net> (raw)
In-Reply-To: <20190120003334.9571-1-daniel@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Sun, 20 Jan 2019 01:33:34 +0100
> The following pull-request contains BPF updates for your *net* tree.
>
> The main changes are:
>
> 1) Fix a out-of-bounds access in __bpf_redirect_no_mac, from Willem.
>
> 2) Fix bpf_setsockopt to reset sock dst on SO_MARK changes, from Peter.
>
> 3) Fix map in map masking to prevent out-of-bounds access under
> speculative execution, from Daniel.
>
> 4) Fix bpf_setsockopt's SO_MAX_PACING_RATE to support TCP internal
> pacing, from Yuchung.
>
> 5) Fix json writer license in bpftool, from Thomas.
>
> 6) Fix AF_XDP to check if an actually queue exists during umem
> setup, from Krzysztof.
>
> 7) Several fixes to BPF stackmap's build id handling. Another fix
> for bpftool build to account for libbfd variations wrt linking
> requirements, from Stanislav.
>
> 8) Fix BPF samples build with clang by working around missing asm
> goto, from Yonghong.
>
> 9) Fix libbpf to retry program load on signal interrupt, from Lorenz.
>
> 10) Various minor compile warning fixes in BPF code, from Mathieu.
>
> Please consider pulling these changes from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git
Pulled, thanks Daniel.
prev parent reply other threads:[~2019-01-20 0:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 0:33 pull-request: bpf 2019-01-20 Daniel Borkmann
2019-01-20 0:44 ` 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=20190119.164436.335693369841017747.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).