linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Cc: acme@kernel.org, Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: [BUG] perf tools: Build failure in v6.16-rc1
Date: Tue, 10 Jun 2025 11:34:44 -0700	[thread overview]
Message-ID: <aEh6xO14wDSCFUDr@google.com> (raw)

Hello,

I've updated the perf-tools-next to v6.16-rc1 and found a build error
like below on alpine linux 3.18.

  In file included from bench/futex.c:6:
  /usr/include/sys/prctl.h:88:8: error: redefinition of 'struct prctl_mm_map'
     88 | struct prctl_mm_map {
        |        ^~~~~~~~~~~~
  In file included from bench/futex.c:5:
  /linux/tools/include/uapi/linux/prctl.h:134:8: note: originally defined here
    134 | struct prctl_mm_map {
        |        ^~~~~~~~~~~~
  make[4]: *** [/linux/tools/build/Makefile.build:86: /build/bench/futex.o] Error 1

git bisect says it's the first commit introduced the failure.

commit 60035a3981a7f9d965df81a48a07b94e52ccd54f
Author: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date:   Wed Apr 16 18:29:19 2025 +0200

    tools/perf: Allow to select the number of hash buckets
    
    Add the -b/ --buckets argument to specify the number of hash buckets for
    the private futex hash. This is directly passed to
        prctl(PR_FUTEX_HASH, PR_FUTEX_HASH_SET_SLOTS, buckets, immutable)
    
    and must return without an error if specified. The `immutable' is 0 by
    default and can be set to 1 via the -I/ --immutable argument.
    The size of the private hash is verified with PR_FUTEX_HASH_GET_SLOTS.
    If PR_FUTEX_HASH_GET_SLOTS failed then it is assumed that an older
    kernel was used without the support and that the global hash is used.
    
    Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Link: https://lore.kernel.org/r/20250416162921.513656-20-bigeasy@linutronix.de

Thanks,
Namhyung


             reply	other threads:[~2025-06-10 18:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 18:34 Namhyung Kim [this message]
2025-06-11  9:25 ` [BUG] perf tools: Build failure in v6.16-rc1 Sebastian Andrzej Siewior
2025-06-11 13:14   ` Arnaldo Carvalho de Melo
2025-06-11 14:55     ` Arnaldo Carvalho de Melo
2025-06-11 15:06       ` Sebastian Andrzej Siewior
2025-06-11 19:01         ` Arnaldo Carvalho de Melo
2025-06-11 21:50           ` Namhyung Kim
2025-06-12  6:25           ` Sebastian Andrzej Siewior

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=aEh6xO14wDSCFUDr@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).