From: Philip Li <philip.li@intel.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: kernel test robot <lkp@intel.com>, <llvm@lists.linux.dev>,
<oe-kbuild-all@lists.linux.dev>
Subject: Re: [linux-next:master 5302/7547] fs/open.c:152:1: error: unknown warning group '-Wattribute-alias', ignored
Date: Wed, 27 May 2026 21:17:09 +0800 [thread overview]
Message-ID: <ahbu1bxuu3wt842q@rli9-mobl> (raw)
In-Reply-To: <20260523005204.GA520407@ax162>
On Fri, May 22, 2026 at 05:52:04PM -0700, Nathan Chancellor wrote:
> On Fri, May 22, 2026 at 02:18:49AM +0800, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: 550604d6c9b9efc8d068aff94dc301694a7afdee
> > commit: bc5ffe737f56ee2734597069ed71f48830549483 [5302/7547] Disable -Wattribute-alias for clang-23 and newer
> > config: arm-defconfig (https://download.01.org/0day-ci/archive/20260522/202605220247.dQAHslyv-lkp@intel.com/config)
> > compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 5bac06718f502014fade905512f1d26d578a18f3)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260522/202605220247.dQAHslyv-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/202605220247.dQAHslyv-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>):
> >
> > >> fs/open.c:152:1: error: unknown warning group '-Wattribute-alias', ignored [-Werror,-Wunknown-warning-option]
> > 152 | SYSCALL_DEFINE2(truncate, const char __user *, path, long, length)
> > | ^
> > include/linux/syscalls.h:226:36: note: expanded from macro 'SYSCALL_DEFINE2'
> > 226 | #define SYSCALL_DEFINE2(name, ...) SYSCALL_DEFINEx(2, _##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:250:2: note: expanded from macro '__SYSCALL_DEFINEx'
> > 250 | __diag_ignore(clang, 23, "-Wattribute-alias", \
> > | ^
> > note: (skipping 4 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
> > include/linux/compiler-clang.h:135:28: note: expanded from macro '__diag_clang_23'
> > 135 | #define __diag_clang_23(s) __diag(s)
> > | ^
> > include/linux/compiler-clang.h:132:20: note: expanded from macro '__diag'
> > 132 | #define __diag(s) _Pragma(__diag_str(clang diagnostic s))
> > | ^
> > <scratch space>:223:27: note: expanded from here
> > 223 | clang diagnostic ignored "-Wattribute-alias"
> > | ^
>
> Please update your clang-23, this will be avoided with a newer version
> from main that has the change that adds -Wattribute-alias.
Thanks Nathan, we will upgrade the clang version asap to avoid this false report.
>
> --
> Cheers,
> Nathan
>
prev parent reply other threads:[~2026-05-27 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 18:18 [linux-next:master 5302/7547] fs/open.c:152:1: error: unknown warning group '-Wattribute-alias', ignored kernel test robot
2026-05-23 0:52 ` Nathan Chancellor
2026-05-27 13:17 ` Philip Li [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=ahbu1bxuu3wt842q@rli9-mobl \
--to=philip.li@intel.com \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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