From: Nathan Chancellor <nathan@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: "Mike Rapoport (Microsoft)" <rppt@kernel.org>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
David Hildenbrand <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
mm-commits@vger.kernel.org
Subject: Re: [akpm-mm:mm-unstable 273/420] mm/userfaultfd.c:4475:1: warning: alias and aliasee have different types 'long (int)' and 'long (typeof (__builtin_choose_expr((__builtin_types_compatible_p(typeof ((int)0), typeof (0LL)) || __builtin_types_compatible_p(typeof ((int)0), typeof (0ULL))), 0...
Date: Thu, 28 May 2026 09:45:52 -0700 [thread overview]
Message-ID: <20260528164552.GB1342076@ax162> (raw)
In-Reply-To: <202605282311.BlbuvsRF-lkp@intel.com>
On Thu, May 28, 2026 at 11:28:25PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
> head: 8a74e22643189e0ae339afc91110ddb4cab1941b
> commit: 688eee218159283140c8c4b48429cfe400cb64e4 [273/420] userfaultfd: merge fs/userfaultfd.c into mm/userfaultfd.c
> config: arm-randconfig-003-20260528 (https://download.01.org/0day-ci/archive/20260528/202605282311.BlbuvsRF-lkp@intel.com/config)
> compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 9409c07de6378507397ecdb6f05f628f58110112)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260528/202605282311.BlbuvsRF-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202605282311.BlbuvsRF-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> >> mm/userfaultfd.c:4475:1: warning: alias and aliasee have different types 'long (int)' and 'long (typeof (__builtin_choose_expr((__builtin_types_compatible_p(typeof ((int)0), typeof (0LL)) || __builtin_types_compatible_p(typeof ((int)0), typeof (0ULL))), 0LL, 0L)))' (aka 'long (long)') [-Wattribute-alias]
> 4475 | SYSCALL_DEFINE1(userfaultfd, int, flags)
> | ^
> include/linux/syscalls.h:225:36: note: expanded from macro 'SYSCALL_DEFINE1'
> 225 | #define SYSCALL_DEFINE1(name, ...) SYSCALL_DEFINEx(1, _##name, __VA_ARGS__)
> | ^
> include/linux/syscalls.h:236:2: note: expanded from macro 'SYSCALL_DEFINEx'
> 236 | __SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
> | ^
> include/linux/syscalls.h:251:18: note: expanded from macro '__SYSCALL_DEFINEx'
> 251 | __attribute__((alias(__stringify(__se_sys##name)))); \
> | ^
> mm/userfaultfd.c:4475:1: note: aliasee is declared here
> include/linux/syscalls.h:225:36: note: expanded from macro 'SYSCALL_DEFINE1'
> 225 | #define SYSCALL_DEFINE1(name, ...) SYSCALL_DEFINEx(1, _##name, __VA_ARGS__)
> | ^
> include/linux/syscalls.h:236:2: note: expanded from macro 'SYSCALL_DEFINEx'
> 236 | __SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
> | ^
> include/linux/syscalls.h:255:18: note: expanded from macro '__SYSCALL_DEFINEx'
> 255 | asmlinkage long __se_sys##name(__MAP(x,__SC_LONG,__VA_ARGS__)) \
> | ^
> <scratch space>:46:1: note: expanded from here
> 46 | __se_sys_userfaultfd
> | ^
> 1 warning generated.
Sorry for the noise, this is from a compiler upgrade, not a fault of
the blamed patch. I plan to submit a fix for this to Linus soon:
https://git.kernel.org/nathan/c/175db11786bde9061db526bf1ac5107d915f5163
--
Cheers,
Nathan
prev parent reply other threads:[~2026-05-28 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 15:28 [akpm-mm:mm-unstable 273/420] mm/userfaultfd.c:4475:1: warning: alias and aliasee have different types 'long (int)' and 'long (typeof (__builtin_choose_expr((__builtin_types_compatible_p(typeof ((int)0), typeof (0LL)) || __builtin_types_compatible_p(typeof ((int)0), typeof (0ULL))), 0 kernel test robot
2026-05-28 16:45 ` Nathan Chancellor [this message]
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=20260528164552.GB1342076@ax162 \
--to=nathan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mm-commits@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rppt@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