mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Hou Tao <houtao@huaweicloud.com>, Byeonguk Jeong <jungbu2855@gmail.com>
Cc: andrii@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
	Alexei Starovoitov <ast@kernel.org>,
	bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf] selftests/bpf: Add a copyright notice to lpm_trie_map_get_next_key
Date: Mon, 04 Nov 2024 11:07:38 +0100	[thread overview]
Message-ID: <d5137f25846ebf585383de4d994d388eabab9d60.camel@linux.ibm.com> (raw)
In-Reply-To: <925cb852-df24-81b6-318a-ee6a628d43c7@huaweicloud.com>

On Mon, 2024-11-04 at 09:34 +0800, Hou Tao wrote:
> Hi,
> 
> On 11/3/2024 2:04 PM, Byeonguk Jeong wrote:
> > Hi,
> > 
> > The selftest "verifier_bits_iter/bad words" has been failed with
> > retval 115, while I did not touched anything but a comment.
> > 
> > Do you have any idea why it failed? I am not sure whether it
> > indicates
> > any bugs in the kernel.
> > 
> > Best,
> > Byeonguk
> 
> Sorry for the inconvenience. It seems the test case
> "verifier_bits_iter/bad words" is flaky. It may fail randomly, such
> as
> in [1]. I think calling bpf_probe_read_kernel_common() on 3GB addr
> under
> s390 host may succeed and the content of the memory address will
> decide
> whether the test case will succeed or not. Do not know the reason why
> reading 3GB address succeeds under s390. Hope to get some insight
> from
> Ilya.  I think we could fix the failure first by using NULL as the
> address of bad words just like null_pointer test case does. Will
> merge
> the test in bad_words into the null_pointer case.

Hi,

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.

Also, unfortunately, 0 is a valid address in the s390 kernel address
space.

I wonder if we could use -4095 as an address that cannot be
dereferenced on all platforms?

Best regards,
Ilya

  parent reply	other threads:[~2024-11-04 10:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-03  4:22 Byeonguk Jeong
2024-11-03  6:04 ` Byeonguk Jeong
2024-11-04  1:34   ` Hou Tao
2024-11-04  2:02     ` Byeonguk Jeong
2024-11-05  2:39       ` Hou Tao
2024-11-04 10:07     ` Ilya Leoshkevich [this message]
2024-11-05  2:34       ` Hou Tao
2024-11-05  6:21         ` Hou Tao

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=d5137f25846ebf585383de4d994d388eabab9d60.camel@linux.ibm.com \
    --to=iii@linux.ibm.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=houtao@huaweicloud.com \
    --cc=jungbu2855@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@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

Powered by JetHome