public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev,
	alexei.starovoitov@gmail.com, andrii@kernel.org,
	eddyz87@gmail.com, song@kernel.org, haoluo@google.com,
	yonghong.song@linux.dev, daniel@iogearbox.net,
	kpsingh@kernel.org, sdf@fomichev.me, jolsa@kernel.org,
	john.fastabend@gmail.com, iii@linux.ibm.com,
	jungbu2855@gmail.com, laoar.shao@gmail.com, houtao1@huawei.com,
	xukuohai@huawei.com
Subject: Re: [PATCH bpf] selftests/bpf: Use -4095 as the bad address for bits iterator
Date: Tue, 05 Nov 2024 22:10:54 +0000	[thread overview]
Message-ID: <173084465451.708559.9556991877632475772.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241105043057.3371482-1-houtao@huaweicloud.com>

Hello:

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

On Tue,  5 Nov 2024 12:30:57 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
> 
> As reported by Byeonguk, the bad_words test in verifier_bits_iter.c
> occasionally fails on s390 host. Quoting Ilya's explanation:
> 
>   s390 kernel runs in a completely separate address space, there is no
>   user/kernel split at TASK_SIZE. The same address may be valid in both
>   the kernel and the user address spaces, there is no way to tell by
>   looking at it. The config option related to this property is
>   ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE.
> 
> [...]

Here is the summary with links:
  - [bpf] selftests/bpf: Use -4095 as the bad address for bits iterator
    https://git.kernel.org/bpf/bpf/c/6801cf7890f2

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



      parent reply	other threads:[~2024-11-05 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05  4:30 [PATCH bpf] selftests/bpf: Use -4095 as the bad address for bits iterator Hou Tao
2024-11-05 20:18 ` Ilya Leoshkevich
2024-11-05 22:04   ` Alexei Starovoitov
2024-11-05 22:10 ` 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=173084465451.708559.9556991877632475772.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=houtao1@huawei.com \
    --cc=houtao@huaweicloud.com \
    --cc=iii@linux.ibm.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=jungbu2855@gmail.com \
    --cc=kpsingh@kernel.org \
    --cc=laoar.shao@gmail.com \
    --cc=martin.lau@linux.dev \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=xukuohai@huawei.com \
    --cc=yonghong.song@linux.dev \
    /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