mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hao Ge <hao.ge@linux.dev>
To: Sasha Levin <sashal@kernel.org>
Cc: Shuah Khan <shuah@kernel.org>,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Suren Baghdasaryan <surenb@google.com>
Subject: Re: [PATCH] kselftest: alloc_tag: use the ll64 types on powerpc64
Date: Wed, 4 Nov 2026 09:10:24 +0800	[thread overview]
Message-ID: <d3c8baa0-3ed9-4f3c-805d-86c98a6bdfe7@linux.dev> (raw)
In-Reply-To: <20261103155454.534649-1-sashal@kernel.org>



On 2026/11/3 23:54, Sasha Levin wrote:
> On powerpc64 __u64 is an unsigned long unless __SANE_USERSPACE_TYPES__
> is defined, so printing and scanning the __u64 fields with %llu warns:
> 
>   allocinfo_ioctl_test.c:93:73: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 2 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
> 
> Define __SANE_USERSPACE_TYPES__, as other selftests do.
> 
> Signed-off-by: Sasha Levin <sashal@kernel.org>

Acked-by: Hao Ge <hao.ge@linux.dev>

> ---
> KernelCI's powerpc kselftest builds show this. The define makes the same
> change on alpha and mips64 and none on the other architectures; the
> x86_64 and 32-bit builds don't change.
> 
>  tools/testing/selftests/alloc_tag/allocinfo_ioctl_test.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/tools/testing/selftests/alloc_tag/allocinfo_ioctl_test.c b/tools/testing/selftests/alloc_tag/allocinfo_ioctl_test.c
> index 74fd64b2370cc..18c761fecfde0 100644
> --- a/tools/testing/selftests/alloc_tag/allocinfo_ioctl_test.c
> +++ b/tools/testing/selftests/alloc_tag/allocinfo_ioctl_test.c
> @@ -1,4 +1,5 @@
>  // SPDX-License-Identifier: GPL-2.0-only
> +#define __SANE_USERSPACE_TYPES__
>  
>  /* kselftest for allocinfo ioctl
>   * allocinfo ioctl retrieves allocinfo data through ioctl

  reply	other threads:[~2026-11-04  1:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 15:54 Sasha Levin
2026-11-04  1:10 ` Hao Ge [this message]
2026-11-04  1:15   ` Suren Baghdasaryan

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=d3c8baa0-3ed9-4f3c-805d-86c98a6bdfe7@linux.dev \
    --to=hao.ge@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sashal@kernel.org \
    --cc=shuah@kernel.org \
    --cc=surenb@google.com \
    /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®