From: John Fastabend <john.fastabend@gmail.com>
To: yhs@fb.com, alexei.starovoitov@gmail.com, daniel@iogearbox.net
Cc: bpf@vger.kernel.org, john.fastabend@gmail.com, kernel-team@fb.com
Subject: [bpf PATCH 0/3] verifier fix for assigning 32bit reg to 64bit reg
Date: Fri, 29 May 2020 10:28:21 -0700 [thread overview]
Message-ID: <159077324869.6014.6516130782021506562.stgit@john-Precision-5820-Tower> (raw)
These add a fix for 32 bit to 64 bit assignment introduced with
latest alu32 bounds tracking. The initial fix was proposed by
Yonghong and then I updated it slightly and added a test fix.
@Yonghong feel free to add your signed-off-by back if you want
or at minimal a ACK would be good.
---
John Fastabend (3):
bpf: fix a verifier issue when assigning 32bit reg states to 64bit ones
bpf, selftests: verifier bounds tests need to be updated
bpf, selftests: add a verifier test for assigning 32bit reg states to 64bit ones
kernel/bpf/verifier.c | 10 +++--
tools/testing/selftests/bpf/verifier/bounds.c | 46 +++++++++++++++++--------
2 files changed, 37 insertions(+), 19 deletions(-)
--
Signature
next reply other threads:[~2020-05-29 17:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 17:28 John Fastabend [this message]
2020-05-29 17:28 ` [bpf PATCH 1/3] bpf: fix a verifier issue when assigning 32bit reg states to 64bit ones John Fastabend
2020-05-29 18:40 ` Yonghong Song
2020-05-29 17:28 ` [bpf PATCH 2/3] bpf, selftests: verifier bounds tests need to be updated John Fastabend
2020-05-29 18:41 ` Yonghong Song
2020-05-29 17:29 ` [bpf PATCH 3/3] bpf, selftests: add a verifier test for assigning 32bit reg states to 64bit ones John Fastabend
2020-05-29 20:53 ` [bpf PATCH 0/3] verifier fix for assigning 32bit reg to 64bit reg 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:
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=159077324869.6014.6516130782021506562.stgit@john-Precision-5820-Tower \
--to=john.fastabend@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=yhs@fb.com \
/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).