From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [linux-next:master 11408/11415] lib/tests/longest_symbol_kunit.c:28:14: sparse: sparse: '##' failed: concatenation is not a valid token
Date: Tue, 18 Mar 2025 08:21:07 +0800 [thread overview]
Message-ID: <202503180806.WdbmHQEr-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: lib/tests/longest_symbol_kunit.c:28:14: sparse: sparse: '##' failed: concatenation is not a valid token"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Kees Cook <kees@kernel.org>
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: e94bd4ec45ac156616da285a0bf03056cd7430fc
commit: 8d483b174d31ef9aff98089d67401e6fc6ad4ea7 [11408/11415] Merge branch 'for-next/kspp' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
:::::: branch date: 11 hours ago
:::::: commit date: 13 hours ago
config: csky-randconfig-r131-20250318 (https://download.01.org/0day-ci/archive/20250318/202503180806.WdbmHQEr-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250318/202503180806.WdbmHQEr-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/r/202503180806.WdbmHQEr-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> lib/tests/longest_symbol_kunit.c:28:14: sparse: sparse: '##' failed: concatenation is not a valid token
>> lib/tests/longest_symbol_kunit.c:28:14: sparse: sparse: '##' failed: concatenation is not a valid token
lib/tests/longest_symbol_kunit.c:29:14: sparse: sparse: '##' failed: concatenation is not a valid token
lib/tests/longest_symbol_kunit.c:29:14: sparse: sparse: '##' failed: concatenation is not a valid token
lib/tests/longest_symbol_kunit.c:34:23: sparse: sparse: '##' failed: concatenation is not a valid token
lib/tests/longest_symbol_kunit.c:34:23: sparse: sparse: '##' failed: concatenation is not a valid token
lib/tests/longest_symbol_kunit.c:37:1: sparse: sparse: '##' failed: concatenation is not a valid token
lib/tests/longest_symbol_kunit.c:37:1: sparse: sparse: '##' failed: concatenation is not a valid token
lib/tests/longest_symbol_kunit.c:41:9: sparse: sparse: '##' failed: concatenation is not a valid token
lib/tests/longest_symbol_kunit.c:41:9: sparse: sparse: '##' failed: concatenation is not a valid token
lib/tests/longest_symbol_kunit.c:64:47: sparse: sparse: '##' failed: concatenation is not a valid token
lib/tests/longest_symbol_kunit.c:64:47: sparse: sparse: '##' failed: concatenation is not a valid token
lib/tests/longest_symbol_kunit.c:28:14: sparse: sparse: Expected ; at end of declaration
lib/tests/longest_symbol_kunit.c:28:14: sparse: sparse: got nnnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7n
lib/tests/longest_symbol_kunit.c:29:14: sparse: sparse: Expected ; at end of declaration
lib/tests/longest_symbol_kunit.c:29:14: sparse: sparse: got nnnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7n
lib/tests/longest_symbol_kunit.c:32:1: sparse: sparse: Expected ; at the end of type declaration
lib/tests/longest_symbol_kunit.c:32:1: sparse: sparse: got }
lib/tests/longest_symbol_kunit.c:41:9: sparse: sparse: Expected ) after typeof
lib/tests/longest_symbol_kunit.c:41:9: sparse: sparse: got nnnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nnng1h2i3j4k5l6m7ng1h2i3j4k5l6m7nng1h2i3j4k5l6m7ng1h2i3j4k5l6m7n
lib/tests/longest_symbol_kunit.c:41:9: sparse: sparse: undefined identifier '__right'
lib/tests/longest_symbol_kunit.c:41:9: sparse: sparse: undefined identifier '__right'
vim +28 lib/tests/longest_symbol_kunit.c
c104c16073b7fd lib/longest_symbol_kunit.c Sergio González Collado 2025-03-02 27
c104c16073b7fd lib/longest_symbol_kunit.c Sergio González Collado 2025-03-02 @28 noinline int LONGEST_SYM_NAME(void);
c104c16073b7fd lib/longest_symbol_kunit.c Sergio González Collado 2025-03-02 29 noinline int LONGEST_SYM_NAME(void)
c104c16073b7fd lib/longest_symbol_kunit.c Sergio González Collado 2025-03-02 30 {
c104c16073b7fd lib/longest_symbol_kunit.c Sergio González Collado 2025-03-02 31 return RETURN_LONGEST_SYM;
c104c16073b7fd lib/longest_symbol_kunit.c Sergio González Collado 2025-03-02 32 }
c104c16073b7fd lib/longest_symbol_kunit.c Sergio González Collado 2025-03-02 33
:::::: The code at line 28 was first introduced by commit
:::::: c104c16073b7fdb3e4eae18f66f4009f6b073d6f Kunit to check the longest symbol length
:::::: TO: Sergio González Collado <sergio.collado@gmail.com>
:::::: CC: Shuah Khan <shuah@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-18 0:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202503180806.WdbmHQEr-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.