mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [linus:master] [selftests/futex]  0ecb4232fc: kernel-selftests.futex/functional.make.fail
Date: Tue, 15 Jul 2025 09:57:35 +0200	[thread overview]
Message-ID: <20250715075735.tdXLHcEA@linutronix.de> (raw)
In-Reply-To: <202507150858.bedaf012-lkp@intel.com>

On 2025-07-15 15:36:13 [+0800], kernel test robot wrote:
> 
> 
> Hello,
> 
> kernel test robot noticed "kernel-selftests.futex/functional.make.fail" on:
> 
> commit: 0ecb4232fc65e659ca7020f8bb2e0fc347acfb7d ("selftests/futex: Set the home_node in futex_numa_mpol")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> 
> [test failed on linus/master      bc9ff192a6c940d9a26e21a0a82f2667067aaf5f]
> [test failed on linux-next/master b551c4e2a98a177a06148cf16505643cd2108386]
> 
> in testcase: kernel-selftests
> version: kernel-selftests-x86_64-7ff71e6d9239-1_20250215
> with following parameters:
> 
> 	group: futex
…
> make[1]: Entering directory '/usr/src/perf_selftests-x86_64-rhel-9.4-kselftests-0ecb4232fc65e659ca7020f8bb2e0fc347acfb7d/tools/testing/selftests/futex/functional'
…
> futex_numa_mpol.c: In function ‘main’:
> futex_numa_mpol.c:213:31: warning: implicit declaration of function ‘numa_set_mempolicy_home_node’; did you mean ‘SYS_set_mempolicy_home_node’? [-Wimplicit-function-declaration]
>   213 |                         ret = numa_set_mempolicy_home_node(futex_ptr, mem_size, i, 0);
>       |                               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
>       |                               SYS_set_mempolicy_home_node

I assume libnuma-dev is around because there are not any other warnings.
That is unfortunate but it seems that numa_set_mempolicy_home_node() is
only around since v2.0.18.
Is and update doable? Otherwise I would have to disable the test.

Sebastian

  reply	other threads:[~2025-07-15  7:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15  7:36 kernel test robot
2025-07-15  7:57 ` Sebastian Andrzej Siewior [this message]
2025-07-15  9:52   ` [PATCH] selftests/futex: Compile also on libnuma < 2.0.16 Sebastian Andrzej Siewior
2025-07-21 17:22     ` Thomas Gleixner
2025-08-18 13:54       ` [PATCH v2] " Sebastian Andrzej Siewior
2026-03-06 17:53         ` Davidlohr Bueso

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=20250715075735.tdXLHcEA@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=peterz@infradead.org \
    --cc=vbabka@suse.cz \
    /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®