public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Add selftest deny_namespace to s390x deny list
Date: Thu, 06 Oct 2022 15:30:16 +0000	[thread overview]
Message-ID: <166507021634.23640.373748112138514966.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221006053429.3549165-1-yhs@fb.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Wed, 5 Oct 2022 22:34:29 -0700 you wrote:
> BPF CI reported that selftest deny_namespace failed with s390x.
> 
>   test_unpriv_userns_create_no_bpf:PASS:no-bpf unpriv new user ns 0 nsec
>   test_deny_namespace:PASS:skel load 0 nsec
>   libbpf: prog 'test_userns_create': failed to attach: ERROR: strerror_r(-524)=22
>   libbpf: prog 'test_userns_create': failed to auto-attach: -524
>   test_deny_namespace:FAIL:attach unexpected error: -524 (errno 524)
>   #57/1    deny_namespace/unpriv_userns_create_no_bpf:FAIL
>   #57      deny_namespace:FAIL
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Add selftest deny_namespace to s390x deny list
    https://git.kernel.org/bpf/bpf-next/c/8206e4e95230

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-10-06 15:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06  5:34 [PATCH bpf-next] selftests/bpf: Add selftest deny_namespace to s390x deny list Yonghong Song
2022-10-06  7:27 ` Jiri Olsa
2022-10-06 15:30 ` 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=166507021634.23640.373748112138514966.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --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