From: Al Viro <viro@zeniv.linux.org.uk>
To: kernel test robot <lkp@intel.com>
Cc: Andrey Albershteyn <aalbersh@kernel.org>,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>,
Amir Goldstein <amir73il@gmail.com>,
"Darrick J. Wong" <djwong@kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: fs/file_attr.c:263:9: error: unexpected token, expected comma
Date: Fri, 2 Jan 2026 10:27:30 +0000 [thread overview]
Message-ID: <20260102102730.GH1712166@ZenIV> (raw)
In-Reply-To: <20260102093114.GG1712166@ZenIV>
On Fri, Jan 02, 2026 at 09:31:14AM +0000, Al Viro wrote:
> On Thu, Jan 01, 2026 at 09:41:43AM +0800, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 9528d5c091c59b408a754a1823cf0942069867cc
> > commit: 2f952c9e8fe13c6ee15c05189f1f87c1a70b866c fs: split fileattr related helpers into separate file
> > date: 6 months ago
> > config: mips-randconfig-r051-20251231 (https://download.01.org/0day-ci/archive/20260101/202601010950.QjCTROwO-lkp@intel.com/config)
> > compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project f43d6834093b19baf79beda8c0337ab020ac5f17)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260101/202601010950.QjCTROwO-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/202601010950.QjCTROwO-lkp@intel.com/
>
> It has nothing whatsoever to do with the commit in question; I would be
> very surprised if the same build was not full of identical errors all
> over the place, wherever we happen to use put_user() or get_user().
>
> Basically, you've stumbled across a mips config that breaks something
> in their asm/uaccess.h; apparently 32bit with EVA, bringing the macro
> horrors from asm-eva.h into play.
FWIW, error message is misleading - it's complaining about the stuff
coming out of inline asm; the token in question is assembler rather than
C one.
Does clang/mips even know about .set eva, seeing that it insists on examining
the inline asm for assembler validity?
Considering this
; cat >/tmp/foo.c <<'EOF'
void f(void)
{
asm volatile(".set push\n.set eva\n.set pop");
}
EOF
; clang --target=mipsel-linux-gnu -mabi=32 -EL -march=mips32r2 -c /tmp/foo.c
/tmp/foo.c:3:27: error: unexpected token, expected comma
3 | asm volatile(".set push\n.set eva\n.set pop");
| ^
<inline asm>:2:9: note: instantiated into assembly here
2 | .set eva
| ^
1 error generated.
;
I rather suspect that it doesn't... FWIW, replacing clang --target=mipsel-linux-gnu
with mips-linux-gnu-gcc works as expected. If you turn that mips32r2 into e.g.
mips32, gcc will spew
/tmp/ccGqqn3X.s: Assembler messages:
/tmp/ccGqqn3X.s:26: Warning: the `eva' extension requires MIPS32 revision 2 or greater
prev parent reply other threads:[~2026-01-02 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-01 1:41 fs/file_attr.c:263:9: error: unexpected token, expected comma kernel test robot
2026-01-02 9:31 ` Al Viro
2026-01-02 10:27 ` Al Viro [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=20260102102730.GH1712166@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=aalbersh@kernel.org \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.