mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "André Almeida" <andrealmeid@igalia.com>
To: Waiman Long <longman@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Shuah Khan <shuah@kernel.org>, Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kselftest@vger.kernel.org,
	Colin Ian King <colin.i.king@gmail.com>,
	Darren Hart <dvhart@infradead.org>,
	Davidlohr Bueso <dave@stgolabs.net>
Subject: Re: [PATCH] selftests/futex: Fix some futex_numa_mpol subtests
Date: Tue, 19 Aug 2025 09:22:49 -0300	[thread overview]
Message-ID: <336a1a43-54ac-4f53-b3a8-5e46f6d45359@igalia.com> (raw)
In-Reply-To: <20250810222742.290485-1-longman@redhat.com>

Hi Waiman,

Em 10/08/2025 19:27, Waiman Long escreveu:
> The "Memory out of range" subtest of futex_numa_mpol assumes that memory
> access outside of the mmap'ed area is invalid. That may not be the case
> depending on the actual memory layout of the test application. When
> that subtest was run on an x86-64 system with latest upstream kernel,
> the test passed as an error was returned from futex_wake(). On another
> powerpc system, the same subtest failed because futex_wake() returned 0.
> 
>    Bail out! futex2_wake(64, 0x86) should fail, but didn't
> 
> Looking further into the passed subtest on x86-64, it was found that an
> -EINVAL was returned instead of -EFAULT. The -EINVAL error was returned
> because the node value test with FLAGS_NUMA set failed with a node value
> of 0x7f7f. IOW, the futex memory was accessible and futex_wake() failed
> because the supposed node number wasn't valid. If that memory location
> happens to have a very small value (e.g. 0), the test will pass and no
> error will be returned.
> 
> Since this subtest is non-deterministic, it is dropped unless we
> explicitly set a guard page beyond the mmap region.
> 
>
I had proposed a refactor of the futex selftests[1] and I spotted the 
same issue with the memory out of range test. My solution for this was 
to create a "buffer zone" with PROT_NONE to ensure that I would have a 
invalid memory access:

/*
  * test_harness_run() calls mmap(..., MAP_SHARED, ...), which can create
  * a valid access memory region just bellow the mmap() issue here. Then,
  * the test for "Memory out of range" will fail because it will succeed
  * accessing the memory address after the range. To avoid this we create
  * a "Buffer zone" with PROT_NONE between the two mmap's.
  */
buffer_zone = mmap(NULL, mem_size, PROT_NONE, MAP_PRIVATE | 
MAP_ANONYMOUS, 0, 0);

[1] 
https://lore.kernel.org/lkml/20250704-tonyk-robust_test_cleanup-v1-13-c0ff4f24c4e1@igalia.com/

  parent reply	other threads:[~2025-08-19 12:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-10 22:27 Waiman Long
2025-08-18 15:54 ` Waiman Long
2025-08-19  7:32 ` Sebastian Andrzej Siewior
2025-08-19 12:22 ` André Almeida [this message]
2025-08-19 19:46   ` Waiman Long

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=336a1a43-54ac-4f53-b3a8-5e46f6d45359@igalia.com \
    --to=andrealmeid@igalia.com \
    --cc=bigeasy@linutronix.de \
    --cc=colin.i.king@gmail.com \
    --cc=dave@stgolabs.net \
    --cc=dvhart@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®