From: Martin KaFai Lau <martin.lau@linux.dev>
To: Jiri Olsa <jolsa@kernel.org>
Cc: Ilya Leoshkevich <iii@linux.ibm.com>, bpf <bpf@vger.kernel.org>
Subject: [TEST FAILURE] bpf: s390: missed/kprobe_recursion
Date: Thu, 23 Jan 2025 14:32:38 -0800 [thread overview]
Message-ID: <3c841f0a-772a-406c-9888-f8e71826daff@linux.dev> (raw)
Hi Jiri,
The "missed/kprobe_recursion" fails consistently on s390. It seems to start
failing after the recent bpf and bpf-next tree ffwd.
An example:
https://github.com/kernel-patches/bpf/actions/runs/12934431612/job/36076956920
Can you help to take a look?
afaict, it only happens on s390 so far, so cc IIya if there is any recent change
that may ring the bell.
Thanks,
Martin
next reply other threads:[~2025-01-23 22:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 22:32 Martin KaFai Lau [this message]
2025-01-24 11:23 ` [TEST FAILURE] bpf: s390: missed/kprobe_recursion Jiri Olsa
2025-01-24 15:41 ` Jiri Olsa
2025-01-26 14:40 ` Masami Hiramatsu
2025-01-26 22:06 ` Jiri Olsa
2025-01-27 19:09 ` Andrii Nakryiko
2025-01-28 4:57 ` Masami Hiramatsu
-- strict thread matches above, loose matches on Subject: below --
2025-01-23 22:32 Martin KaFai Lau
2025-01-23 22:44 ` Martin KaFai Lau
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=3c841f0a-772a-406c-9888-f8e71826daff@linux.dev \
--to=martin.lau@linux.dev \
--cc=bpf@vger.kernel.org \
--cc=iii@linux.ibm.com \
--cc=jolsa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.