bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: alexei.starovoitov@gmail.com
Cc: jannh@google.com, yhs@fb.com, john.fastabend@gmail.com,
	bpf@vger.kernel.org, netdev@vger.kernel.org,
	Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH bpf-next 0/3] Fix __reg_bound_offset32 handling
Date: Mon, 30 Mar 2020 18:03:21 +0200	[thread overview]
Message-ID: <20200330160324.15259-1-daniel@iogearbox.net> (raw)

Fix for the verifier's __reg_bound_offset32() handling, please see individual
patches for details.


Daniel Borkmann (1):
  bpf: Undo incorrect __reg_bound_offset32 handling

Jann Horn (2):
  bpf: Fix tnum constraints for 32-bit comparisons
  bpf: Simplify reg_set_min_max_inv handling

 kernel/bpf/verifier.c | 227 +++++++++++++++++-------------------------
 1 file changed, 90 insertions(+), 137 deletions(-)


             reply	other threads:[~2020-03-30 16:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30 16:03 Daniel Borkmann [this message]
2020-03-30 16:03 ` [PATCH bpf-next 1/3] bpf: Undo incorrect __reg_bound_offset32 handling Daniel Borkmann
2020-03-30 16:03 ` [PATCH bpf-next 2/3] bpf: Fix tnum constraints for 32-bit comparisons Daniel Borkmann
2020-03-30 16:03 ` [PATCH bpf-next 3/3] bpf: Simplify reg_set_min_max_inv handling Daniel Borkmann
2020-03-30 19:01 ` [PATCH bpf-next 0/3] Fix __reg_bound_offset32 handling Alexei Starovoitov

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200330160324.15259-1-daniel@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=jannh@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=yhs@fb.com \


* 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).