From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net, jolsa@redhat.com
Subject: Re: [RFC PATCH] bpf: s390: add JIT support for multi-function programs
Date: Tue, 27 Aug 2019 15:21:30 +0200 [thread overview]
Message-ID: <3F7BF2AC-E27D-4E69-90D6-07B36C7D7598@linux.ibm.com> (raw)
In-Reply-To: <20190826182036.17456-1-yauheni.kaliuta@redhat.com>
> Am 26.08.2019 um 20:20 schrieb Yauheni Kaliuta <yauheni.kaliuta@redhat.com>:
>
> test_verifier (5.3-rc6):
>
> without patch:
> Summary: 1501 PASSED, 0 SKIPPED, 47 FAILED
>
> with patch:
> Summary: 1540 PASSED, 0 SKIPPED, 8 FAILED
Are you per chance running with a testsuite patch like this one?
--- a/tools/testing/selftests/bpf/test_verifier.c
+++ b/tools/testing/selftests/bpf/test_verifier.c
@@ -846,7 +846,7 @@ static int do_prog_test_run(int fd_prog, bool unpriv, uint32_t expected_val,
tmp, &size_tmp, &retval, NULL);
if (unpriv)
set_admin(false);
- if (err && errno != 524/*ENOTSUPP*/ && errno != EPERM) {
+ if (err && errno != EPERM) {
printf("Unexpected bpf_prog_test_run error ");
return err;
}
Without it, all the failures appear to be masked for me.
next prev parent reply other threads:[~2019-08-27 13:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 18:20 [RFC PATCH] bpf: s390: add JIT support for multi-function programs Yauheni Kaliuta
2019-08-27 13:21 ` Ilya Leoshkevich [this message]
2019-08-27 13:46 ` Ilya Leoshkevich
2019-08-27 14:21 ` Yauheni Kaliuta
2019-08-27 14:37 ` Ilya Leoshkevich
2019-08-27 14:48 ` Yauheni Kaliuta
2019-08-27 14:25 ` Yauheni Kaliuta
2019-08-27 14:46 ` Ilya Leoshkevich
2019-08-27 15:05 ` Yauheni Kaliuta
2019-08-27 14:53 ` [PATCH v2] " Yauheni Kaliuta
2019-08-27 16:39 ` Ilya Leoshkevich
2019-08-28 9:11 ` Ilya Leoshkevich
2019-08-28 18:28 ` [PATCH v3] " Yauheni Kaliuta
2019-08-29 8:52 ` Ilya Leoshkevich
2019-08-30 23:22 ` Daniel Borkmann
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=3F7BF2AC-E27D-4E69-90D6-07B36C7D7598@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@redhat.com \
--cc=yauheni.kaliuta@redhat.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