netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: daniel@iogearbox.net, ast@kernel.org, netdev@vger.kernel.org
Subject: pull-request: bpf 2018-01-18
Date: Thu, 18 Jan 2018 02:16:03 +0100	[thread overview]
Message-ID: <20180118011603.14659-1-daniel@iogearbox.net> (raw)

Hi David,

The following pull-request contains BPF updates for your *net* tree.

The main changes are:

1) Fix a divide by zero due to wrong if (src_reg == 0) check in
   64-bit mode. Properly handle this in interpreter and mask it
   also generically in verifier to guard against similar checks
   in JITs, from Eric and Alexei.

2) Fix a bug in arm64 JIT when tail calls are involved and progs
   have different stack sizes, from Daniel.

3) Reject stores into BPF context that are not expected BPF_STX |
   BPF_MEM variant, from Daniel.

4) Mark dst reg as unknown on {s,u}bounds adjustments when the
   src reg has derived bounds from dead branches, from Daniel.

Please consider pulling these changes from:

  git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git

Thanks a lot!

----------------------------------------------------------------

The following changes since commit 8155aedf512edd3f88ef19f7cacf476ace7d1322:

  Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf (2018-01-14 11:01:33 -0500)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git 

for you to fetch changes up to 6f16101e6a8b4324c36e58a29d9e0dbb287cdedb:

  bpf: mark dst unknown on inconsistent {s, u}bounds adjustments (2018-01-17 16:23:17 -0800)

----------------------------------------------------------------
Alexei Starovoitov (1):
      bpf: fix 32-bit divide by zero

Daniel Borkmann (3):
      bpf, arm64: fix stack_depth tracking in combination with tail calls
      bpf: reject stores into ctx via st and xadd
      bpf: mark dst unknown on inconsistent {s, u}bounds adjustments

Eric Dumazet (1):
      bpf: fix divides by zero

 arch/arm64/net/bpf_jit_comp.c               |  20 ++--
 kernel/bpf/core.c                           |   4 +-
 kernel/bpf/verifier.c                       |  64 ++++++++++--
 net/core/filter.c                           |   4 +
 tools/testing/selftests/bpf/test_verifier.c | 152 +++++++++++++++++++++++++++-
 5 files changed, 219 insertions(+), 25 deletions(-)

             reply	other threads:[~2018-01-18  1:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18  1:16 Daniel Borkmann [this message]
2018-01-18 14:23 ` pull-request: bpf 2018-01-18 David Miller

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=20180118011603.14659-1-daniel@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ast@kernel.org \
    --cc=davem@davemloft.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).