From: Al Viro <viro@zeniv.linux.org.uk>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: fs/namei.c:232:6: error: unexpected token, expected comma
Date: Sun, 20 Apr 2025 07:50:03 +0100 [thread overview]
Message-ID: <20250420065003.GT2023217@ZenIV> (raw)
In-Reply-To: <202504090937.ZGGFamL2-lkp@intel.com>
On Wed, Apr 09, 2025 at 07:23:35AM +0800, kernel test robot wrote:
> fs/namei.c:232:6: error: instruction requires a CPU feature not currently enabled
> 232 | if (get_user(c, pathname))
> | ^
> arch/mips/include/asm/uaccess.h:97:33: note: expanded from macro 'get_user'
> 97 | access_ok(__p, sizeof(*__p)) ? __get_user((x), __p) : \
> | ^
> arch/mips/include/asm/uaccess.h:177:23: note: expanded from macro '__get_user'
> 177 | __get_data_asm((x), user_lb, __gu_ptr); \
> | ^
> <inline asm>:4:2: note: instantiated into assembly here
> 4 | lbe $3, 0($4)
> | ^
Wrong cc(1) options, perhaps? CONFIG_CPU_MIPS32_3_5_EVA (and CONFIG_EVA) are
present in your .config, so...
Looks like that's one for mips (and clang) folks...
prev parent reply other threads:[~2025-04-20 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 23:23 fs/namei.c:232:6: error: unexpected token, expected comma kernel test robot
2025-04-20 6:50 ` 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=20250420065003.GT2023217@ZenIV \
--to=viro@zeniv.linux.org.uk \
--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.