From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Cc: bpf@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH 0/5] s390/bpf: fix lib/test_bpf.c failures
Date: Fri, 17 Jul 2020 18:53:21 +0200 [thread overview]
Message-ID: <20200717165326.6786-1-iii@linux.ibm.com> (raw)
This patch series fixes three regressions caused by 4e9b4a6883dd
("s390/bpf: Use relative long branches") reported by Seth Forshee
(patches 2-4) and adds two minor related improvements (patches 1
and 5).
Ilya Leoshkevich (5):
selftests: bpf: test_kmod.sh: fix running out of srctree
s390/bpf: fix sign extension in branch_ku
s390/bpf: use brcl for jumping to exit_ip if necessary
s390/bpf: tolerate not converging code shrinking
s390/bpf: use bpf_skip() in bpf_jit_prologue()
arch/s390/net/bpf_jit_comp.c | 63 +++++++++++++++---------
tools/testing/selftests/bpf/test_kmod.sh | 12 +++--
2 files changed, 50 insertions(+), 25 deletions(-)
--
2.25.4
next reply other threads:[~2020-07-17 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 16:53 Ilya Leoshkevich [this message]
2020-07-17 16:53 ` [PATCH 1/5] selftests: bpf: test_kmod.sh: fix running out of srctree Ilya Leoshkevich
2020-07-17 16:53 ` [PATCH 2/5] s390/bpf: fix sign extension in branch_ku Ilya Leoshkevich
2020-07-17 22:23 ` Seth Forshee
2020-07-17 16:53 ` [PATCH 3/5] s390/bpf: use brcl for jumping to exit_ip if necessary Ilya Leoshkevich
2020-07-17 16:53 ` [PATCH 4/5] s390/bpf: tolerate not converging code shrinking Ilya Leoshkevich
2020-07-17 16:53 ` [PATCH 5/5] s390/bpf: use bpf_skip() in bpf_jit_prologue() Ilya Leoshkevich
2020-07-21 18:17 ` [PATCH 0/5] s390/bpf: fix lib/test_bpf.c failures 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=20200717165326.6786-1-iii@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.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