From: kernel test robot <lkp@intel.com>
To: Alex Markuze <amarkuze@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 4/5] ceph: Add BLOG debugfs support
Date: Sat, 25 Oct 2025 15:14:08 +0800 [thread overview]
Message-ID: <202510251449.dXsrM1va-lkp@intel.com> (raw)
In-Reply-To: <20251024084259.2359693-5-amarkuze@redhat.com>
Hi Alex,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on akpm-mm/mm-nonmm-unstable]
[also build test ERROR on tip/sched/core linus/master v6.18-rc2 next-20251024]
[cannot apply to ceph-client/testing ceph-client/for-linus]
[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/Alex-Markuze/sched-fork-Wire-BLOG-contexts-into-task-lifecycle/20251024-164832
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-nonmm-unstable
patch link: https://lore.kernel.org/r/20251024084259.2359693-5-amarkuze%40redhat.com
patch subject: [RFC PATCH 4/5] ceph: Add BLOG debugfs support
config: i386-buildonly-randconfig-005-20251025 (https://download.01.org/0day-ci/archive/20251025/202510251449.dXsrM1va-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251025/202510251449.dXsrM1va-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/202510251449.dXsrM1va-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from fs/ceph/debugfs.c:23:
In file included from include/linux/ceph/ceph_blog.h:10:
In file included from include/linux/blog/blog.h:17:
>> include/linux/blog/blog_ser.h:120:16: error: static assertion failed due to requirement 'sizeof (null_str.str) == sizeof(unsigned long)': null_str.str size must match unsigned long for proper alignment
120 | static_assert(sizeof(null_str.str) == sizeof(unsigned long),
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/build_bug.h:77:50: note: expanded from macro 'static_assert'
77 | #define static_assert(expr, ...) __static_assert(expr, ##__VA_ARGS__, #expr)
| ^~~~
include/linux/build_bug.h:78:56: note: expanded from macro '__static_assert'
78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
| ^~~~
include/linux/blog/blog_ser.h:120:37: note: expression evaluates to '8 == 4'
120 | static_assert(sizeof(null_str.str) == sizeof(unsigned long),
| ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~
include/linux/build_bug.h:77:50: note: expanded from macro 'static_assert'
77 | #define static_assert(expr, ...) __static_assert(expr, ##__VA_ARGS__, #expr)
| ^~~~
include/linux/build_bug.h:78:56: note: expanded from macro '__static_assert'
78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
| ^~~~
fs/ceph/debugfs.c:407:2: error: call to undeclared function 'boutc'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
407 | boutc(fsc->client, "begin\n");
| ^
fs/ceph/debugfs.c:429:2: error: call to undeclared function 'boutc'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
429 | boutc(fsc->client, "begin\n");
| ^
3 errors generated.
--
In file included from debugfs.c:23:
In file included from include/linux/ceph/ceph_blog.h:10:
In file included from include/linux/blog/blog.h:17:
>> include/linux/blog/blog_ser.h:120:16: error: static assertion failed due to requirement 'sizeof (null_str.str) == sizeof(unsigned long)': null_str.str size must match unsigned long for proper alignment
120 | static_assert(sizeof(null_str.str) == sizeof(unsigned long),
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/build_bug.h:77:50: note: expanded from macro 'static_assert'
77 | #define static_assert(expr, ...) __static_assert(expr, ##__VA_ARGS__, #expr)
| ^~~~
include/linux/build_bug.h:78:56: note: expanded from macro '__static_assert'
78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
| ^~~~
include/linux/blog/blog_ser.h:120:37: note: expression evaluates to '8 == 4'
120 | static_assert(sizeof(null_str.str) == sizeof(unsigned long),
| ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~
include/linux/build_bug.h:77:50: note: expanded from macro 'static_assert'
77 | #define static_assert(expr, ...) __static_assert(expr, ##__VA_ARGS__, #expr)
| ^~~~
include/linux/build_bug.h:78:56: note: expanded from macro '__static_assert'
78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
| ^~~~
debugfs.c:407:2: error: call to undeclared function 'boutc'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
407 | boutc(fsc->client, "begin\n");
| ^
debugfs.c:429:2: error: call to undeclared function 'boutc'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
429 | boutc(fsc->client, "begin\n");
| ^
3 errors generated.
vim +120 include/linux/blog/blog_ser.h
8ffa1efe9718cb Alex Markuze 2025-10-24 116
8ffa1efe9718cb Alex Markuze 2025-10-24 117 static inline size_t write_null_str(char *dst)
8ffa1efe9718cb Alex Markuze 2025-10-24 118 {
8ffa1efe9718cb Alex Markuze 2025-10-24 119 *(union null_str_u *)dst = null_str;
8ffa1efe9718cb Alex Markuze 2025-10-24 @120 static_assert(sizeof(null_str.str) == sizeof(unsigned long),
8ffa1efe9718cb Alex Markuze 2025-10-24 121 "null_str.str size must match unsigned long for proper alignment");
8ffa1efe9718cb Alex Markuze 2025-10-24 122 return __builtin_strlen(null_str.str);
8ffa1efe9718cb Alex Markuze 2025-10-24 123 }
8ffa1efe9718cb Alex Markuze 2025-10-24 124
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-10-25 7:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 8:42 [RFC PATCH 0/5] BLOG: per-task logging contexts with Ceph consumer Alex Markuze
2025-10-24 8:42 ` [RFC PATCH 1/5] sched, fork: Wire BLOG contexts into task lifecycle Alex Markuze
2025-10-24 17:44 ` Steven Rostedt
2025-10-29 18:57 ` Viacheslav Dubeyko
2025-10-24 8:42 ` [RFC PATCH 2/5] lib: Introduce BLOG (Binary LOGging) subsystem Alex Markuze
2025-10-30 18:47 ` Viacheslav Dubeyko
2025-10-24 8:42 ` [RFC PATCH 3/5] ceph: Add BLOG scaffolding Alex Markuze
2025-11-03 22:37 ` Viacheslav Dubeyko
2025-10-24 8:42 ` [RFC PATCH 4/5] ceph: Add BLOG debugfs support Alex Markuze
2025-10-25 3:56 ` kernel test robot
2025-10-25 7:14 ` kernel test robot [this message]
2025-11-03 21:07 ` Viacheslav Dubeyko
2025-10-24 8:42 ` [RFC PATCH 5/5] ceph: Activate BLOG logging Alex Markuze
2025-10-25 5:08 ` kernel test robot
2025-11-03 21:00 ` Viacheslav Dubeyko
2025-10-24 15:32 ` [RFC PATCH 0/5] BLOG: per-task logging contexts with Ceph consumer David Hildenbrand
2025-10-24 17:53 ` Steven Rostedt
2025-10-25 10:50 ` Alex Markuze
2025-10-25 14:59 ` Steven Rostedt
2025-10-25 17:54 ` Alex Markuze
2025-10-27 14:54 ` Steven Rostedt
2025-10-28 17:07 ` Viacheslav Dubeyko
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=202510251449.dXsrM1va-lkp@intel.com \
--to=lkp@intel.com \
--cc=amarkuze@redhat.com \
--cc=llvm@lists.linux.dev \
--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.