From: kernel test robot <lkp@intel.com>
To: Waiman Long <longman@redhat.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>
Subject: [peterz-queue:locking/core 6/7] kernel/locking/lockdep.c:6017:57: error: 'offset' undeclared; did you mean 'off_t'?
Date: Sat, 12 Feb 2022 13:24:42 +0800 [thread overview]
Message-ID: <202202121348.Uty03Al8-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/core
head: 2300c94a775d0f2a733ef11285cc0abe8126edf6
commit: 065af96d73df2653a2d7da572cf8ba57218479ef [6/7] locking/lockdep: Cleanup reinit_class()
config: i386-randconfig-m021 (https://download.01.org/0day-ci/archive/20220212/202202121348.Uty03Al8-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/commit/?id=065af96d73df2653a2d7da572cf8ba57218479ef
git remote add peterz-queue https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git
git fetch --no-tags peterz-queue locking/core
git checkout 065af96d73df2653a2d7da572cf8ba57218479ef
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from <command-line>:
kernel/locking/lockdep.c: In function 'reinit_class':
>> kernel/locking/lockdep.c:6017:57: error: 'offset' undeclared (first use in this function); did you mean 'off_t'?
6017 | BUILD_BUG_ON(offsetof(struct lock_class, lock_entry) > offset);
| ^~~~~~
include/linux/compiler_types.h:326:9: note: in definition of macro '__compiletime_assert'
326 | if (!(condition)) \
| ^~~~~~~~~
include/linux/compiler_types.h:346:2: note: in expansion of macro '_compiletime_assert'
346 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
| ^~~~~~~~~~~~~~~~~~~
include/linux/build_bug.h:39:37: note: in expansion of macro 'compiletime_assert'
39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
| ^~~~~~~~~~~~~~~~~~
include/linux/build_bug.h:50:2: note: in expansion of macro 'BUILD_BUG_ON_MSG'
50 | BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition)
| ^~~~~~~~~~~~~~~~
kernel/locking/lockdep.c:6017:2: note: in expansion of macro 'BUILD_BUG_ON'
6017 | BUILD_BUG_ON(offsetof(struct lock_class, lock_entry) > offset);
| ^~~~~~~~~~~~
kernel/locking/lockdep.c:6017:57: note: each undeclared identifier is reported only once for each function it appears in
6017 | BUILD_BUG_ON(offsetof(struct lock_class, lock_entry) > offset);
| ^~~~~~
include/linux/compiler_types.h:326:9: note: in definition of macro '__compiletime_assert'
326 | if (!(condition)) \
| ^~~~~~~~~
include/linux/compiler_types.h:346:2: note: in expansion of macro '_compiletime_assert'
346 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
| ^~~~~~~~~~~~~~~~~~~
include/linux/build_bug.h:39:37: note: in expansion of macro 'compiletime_assert'
39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
| ^~~~~~~~~~~~~~~~~~
include/linux/build_bug.h:50:2: note: in expansion of macro 'BUILD_BUG_ON_MSG'
50 | BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition)
| ^~~~~~~~~~~~~~~~
kernel/locking/lockdep.c:6017:2: note: in expansion of macro 'BUILD_BUG_ON'
6017 | BUILD_BUG_ON(offsetof(struct lock_class, lock_entry) > offset);
| ^~~~~~~~~~~~
vim +6017 kernel/locking/lockdep.c
6011
6012 static void reinit_class(struct lock_class *class)
6013 {
6014 WARN_ON_ONCE(!class->lock_entry.next);
6015 WARN_ON_ONCE(!list_empty(&class->locks_after));
6016 WARN_ON_ONCE(!list_empty(&class->locks_before));
> 6017 BUILD_BUG_ON(offsetof(struct lock_class, lock_entry) > offset);
6018 BUILD_BUG_ON(offsetof(struct lock_class, locks_after) > offset);
6019 BUILD_BUG_ON(offsetof(struct lock_class, locks_before) > offset);
6020 memset_startat(class, 0, key);
6021 }
6022
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-12 5:25 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=202202121348.Uty03Al8-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=peterz@infradead.org \
/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