public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Yury Norov (NVIDIA)" <yury.norov@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v3 4/4] tracing: move tracing declarations from kernel.h to a dedicated header
Date: Sun, 7 Dec 2025 01:30:25 +0800	[thread overview]
Message-ID: <202512070100.XPSKmmIG-lkp@intel.com> (raw)
In-Reply-To: <20251205175237.242022-5-yury.norov@gmail.com>

Hi Yury,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-i915/for-linux-next]
[also build test ERROR on drm-i915/for-linux-next-fixes driver-core/driver-core-testing driver-core/driver-core-next driver-core/driver-core-linus linus/master v6.18 next-20251205]
[cannot apply to mcgrof/modules-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Yury-Norov-NVIDIA/kernel-h-drop-STACK_MAGIC-macro/20251206-015505
base:   https://gitlab.freedesktop.org/drm/i915/kernel.git for-linux-next
patch link:    https://lore.kernel.org/r/20251205175237.242022-5-yury.norov%40gmail.com
patch subject: [PATCH v3 4/4] tracing: move tracing declarations from kernel.h to a dedicated header
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20251207/202512070100.XPSKmmIG-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251207/202512070100.XPSKmmIG-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/202512070100.XPSKmmIG-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from arch/x86/purgatory/purgatory.c:18:
>> arch/x86/purgatory/../boot/string.h:11:7: error: expected identifier or '('
      11 | void *memmove(void *dst, const void *src, size_t len);
         |       ^
   include/linux/fortify-string.h:694:27: note: expanded from macro 'memmove'
     694 | #define memmove(p, q, s)  __fortify_memcpy_chk(p, q, s,                 \
         |                           ^
   include/linux/fortify-string.h:626:42: note: expanded from macro '__fortify_memcpy_chk'
     626 |                              p_size_field, q_size_field, op) ({         \
         |                                                               ^
   In file included from arch/x86/purgatory/purgatory.c:18:
>> arch/x86/purgatory/../boot/string.h:11:7: error: expected ')'
   include/linux/fortify-string.h:694:27: note: expanded from macro 'memmove'
     694 | #define memmove(p, q, s)  __fortify_memcpy_chk(p, q, s,                 \
         |                           ^
   include/linux/fortify-string.h:626:42: note: expanded from macro '__fortify_memcpy_chk'
     626 |                              p_size_field, q_size_field, op) ({         \
         |                                                               ^
   arch/x86/purgatory/../boot/string.h:11:7: note: to match this '('
   include/linux/fortify-string.h:694:27: note: expanded from macro 'memmove'
     694 | #define memmove(p, q, s)  __fortify_memcpy_chk(p, q, s,                 \
         |                           ^
   include/linux/fortify-string.h:626:41: note: expanded from macro '__fortify_memcpy_chk'
     626 |                              p_size_field, q_size_field, op) ({         \
         |                                                              ^
   In file included from arch/x86/purgatory/purgatory.c:18:
   arch/x86/purgatory/../boot/string.h:23:15: error: expected identifier or '('
      23 | extern size_t strlen(const char *s);
         |               ^
   include/linux/fortify-string.h:258:2: note: expanded from macro 'strlen'
     258 |         __builtin_choose_expr(__is_constexpr(__builtin_strlen(p)),      \
         |         ^
   3 errors generated.


vim +11 arch/x86/purgatory/../boot/string.h

c041b5ad8640dd Vivek Goyal 2014-03-18   9  
c041b5ad8640dd Vivek Goyal 2014-03-18  10  void *memcpy(void *dst, const void *src, size_t len);
bc7aaf52f96367 Kees Cook   2021-11-19 @11  void *memmove(void *dst, const void *src, size_t len);
c041b5ad8640dd Vivek Goyal 2014-03-18  12  void *memset(void *dst, int c, size_t len);
fb4cac573ef6dc Vivek Goyal 2014-03-18  13  int memcmp(const void *s1, const void *s2, size_t len);
bc7aaf52f96367 Kees Cook   2021-11-19  14  int bcmp(const void *s1, const void *s2, size_t len);
c041b5ad8640dd Vivek Goyal 2014-03-18  15  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

           reply	other threads:[~2025-12-06 17:30 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20251205175237.242022-5-yury.norov@gmail.com>]

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=202512070100.XPSKmmIG-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=yury.norov@gmail.com \
    /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