From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Daniel_M=C3=BCller_=3Cdeso=40posteo=2Enet=3E?=@ci.codeaurora.org
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kafai@fb.com, kernel-team@fb.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Panic on hard/soft lockup
Date: Wed, 26 Oct 2022 06:50:15 +0000 [thread overview]
Message-ID: <166676701557.11097.582825976321869971.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221025231546.811766-1-deso@posteo.net>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 25 Oct 2022 23:15:46 +0000 you wrote:
> When running tests, we should probably accept any help we can get when
> it comes to detecting issues early or making them more debuggable. We
> have seen a few cases where a test_progs_noalu32 run, for example,
> encountered a soft lockup and stopped making progress. It was only
> interrupted once we hit the overall test timeout [0]. We can not and do
> not want to necessarily rely on test timeouts, because those rely on
> infrastructure provided by the environment we run in (and which is not
> present in tools/testing/selftests/bpf/vmtest.sh, for example).
> To that end, let's enable panics on soft as well as hard lockups to fail
> fast should we encounter one. That's happening in the configuration
> indented to be used for selftests (including when using vmtest.sh or
> when running in BPF CI).
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Panic on hard/soft lockup
https://git.kernel.org/bpf/bpf-next/c/5ed88f81511c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-10-26 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 23:15 [PATCH bpf-next] selftests/bpf: Panic on hard/soft lockup Daniel Müller
2022-10-26 6:50 ` patchwork-bot+netdevbpf [this message]
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=166676701557.11097.582825976321869971.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Daniel_M=C3=BCller_=3Cdeso=40posteo=2Enet=3E?=@ci.codeaurora.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=kernel-team@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