From: kernel test robot <lkp@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Ben Widawsky <ben.widawsky@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org
Subject: [cxl:for-5.19/cxl-device-lock 2/12] include/linux/device.h:849:3: error: use of undeclared identifier 'DRV_NAME'
Date: Sat, 9 Apr 2022 14:23:37 +0800 [thread overview]
Message-ID: <202204091427.VqNnQI8Y-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git for-5.19/cxl-device-lock
head: fd011b3bf6035eb145160f266fe0250e1e42b86e
commit: 69d523de7046a14555e4f4986c4682e8c1635740 [2/12] device-core: Add dev->lock_class to enable device_lock() lockdep validation
config: x86_64-randconfig-a005 (https://download.01.org/0day-ci/archive/20220409/202204091427.VqNnQI8Y-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project c29a51b3a257908aebc01cd7c4655665db317d66)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git/commit/?id=69d523de7046a14555e4f4986c4682e8c1635740
git remote add cxl https://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git
git fetch --no-tags cxl for-5.19/cxl-device-lock
git checkout 69d523de7046a14555e4f4986c4682e8c1635740
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 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 drivers/xen/xen-pciback/conf_space.c:17:
In file included from include/linux/pci.h:37:
>> include/linux/device.h:849:3: error: use of undeclared identifier 'DRV_NAME'
dev_warn(dev,
^
include/linux/dev_printk.h:146:54: note: expanded from macro 'dev_warn'
dev_printk_index_wrap(_dev_warn, KERN_WARNING, dev, dev_fmt(fmt), ##__VA_ARGS__)
^
drivers/xen/xen-pciback/conf_space.c:13:22: note: expanded from macro 'dev_fmt'
#define dev_fmt(fmt) DRV_NAME ": " fmt
^
In file included from drivers/xen/xen-pciback/conf_space.c:17:
In file included from include/linux/pci.h:1522:
In file included from include/linux/dmapool.h:14:
In file included from include/linux/scatterlist.h:8:
In file included from include/linux/mm.h:700:
In file included from include/linux/huge_mm.h:8:
In file included from include/linux/fs.h:33:
In file included from include/linux/percpu-rwsem.h:7:
In file included from include/linux/rcuwait.h:6:
In file included from include/linux/sched/signal.h:6:
include/linux/signal.h:97:11: warning: array index 3 is past the end of the array (which contains 1 element) [-Warray-bounds]
return (set->sig[3] | set->sig[2] |
^ ~
arch/x86/include/asm/signal.h:24:2: note: array 'sig' declared here
unsigned long sig[_NSIG_WORDS];
^
In file included from drivers/xen/xen-pciback/conf_space.c:17:
In file included from include/linux/pci.h:1522:
In file included from include/linux/dmapool.h:14:
In file included from include/linux/scatterlist.h:8:
In file included from include/linux/mm.h:700:
In file included from include/linux/huge_mm.h:8:
In file included from include/linux/fs.h:33:
In file included from include/linux/percpu-rwsem.h:7:
In file included from include/linux/rcuwait.h:6:
In file included from include/linux/sched/signal.h:6:
include/linux/signal.h:97:25: warning: array index 2 is past the end of the array (which contains 1 element) [-Warray-bounds]
return (set->sig[3] | set->sig[2] |
^ ~
arch/x86/include/asm/signal.h:24:2: note: array 'sig' declared here
unsigned long sig[_NSIG_WORDS];
^
In file included from drivers/xen/xen-pciback/conf_space.c:17:
In file included from include/linux/pci.h:1522:
In file included from include/linux/dmapool.h:14:
In file included from include/linux/scatterlist.h:8:
In file included from include/linux/mm.h:700:
In file included from include/linux/huge_mm.h:8:
In file included from include/linux/fs.h:33:
In file included from include/linux/percpu-rwsem.h:7:
In file included from include/linux/rcuwait.h:6:
In file included from include/linux/sched/signal.h:6:
include/linux/signal.h:98:4: warning: array index 1 is past the end of the array (which contains 1 element) [-Warray-bounds]
set->sig[1] | set->sig[0]) == 0;
^ ~
arch/x86/include/asm/signal.h:24:2: note: array 'sig' declared here
unsigned long sig[_NSIG_WORDS];
^
In file included from drivers/xen/xen-pciback/conf_space.c:17:
In file included from include/linux/pci.h:1522:
In file included from include/linux/dmapool.h:14:
In file included from include/linux/scatterlist.h:8:
In file included from include/linux/mm.h:700:
In file included from include/linux/huge_mm.h:8:
In file included from include/linux/fs.h:33:
In file included from include/linux/percpu-rwsem.h:7:
In file included from include/linux/rcuwait.h:6:
In file included from include/linux/sched/signal.h:6:
include/linux/signal.h:100:11: warning: array index 1 is past the end of the array (which contains 1 element) [-Warray-bounds]
return (set->sig[1] | set->sig[0]) == 0;
^ ~
arch/x86/include/asm/signal.h:24:2: note: array 'sig' declared here
unsigned long sig[_NSIG_WORDS];
^
In file included from drivers/xen/xen-pciback/conf_space.c:17:
In file included from include/linux/pci.h:1522:
In file included from include/linux/dmapool.h:14:
In file included from include/linux/scatterlist.h:8:
In file included from include/linux/mm.h:700:
In file included from include/linux/huge_mm.h:8:
In file included from include/linux/fs.h:33:
In file included from include/linux/percpu-rwsem.h:7:
In file included from include/linux/rcuwait.h:6:
In file included from include/linux/sched/signal.h:6:
include/linux/signal.h:113:11: warning: array index 3 is past the end of the array (which contains 1 element) [-Warray-bounds]
return (set1->sig[3] == set2->sig[3]) &&
^ ~
arch/x86/include/asm/signal.h:24:2: note: array 'sig' declared here
unsigned long sig[_NSIG_WORDS];
^
In file included from drivers/xen/xen-pciback/conf_space.c:17:
In file included from include/linux/pci.h:1522:
In file included from include/linux/dmapool.h:14:
In file included from include/linux/scatterlist.h:8:
In file included from include/linux/mm.h:700:
In file included from include/linux/huge_mm.h:8:
In file included from include/linux/fs.h:33:
In file included from include/linux/percpu-rwsem.h:7:
In file included from include/linux/rcuwait.h:6:
In file included from include/linux/sched/signal.h:6:
include/linux/signal.h:113:27: warning: array index 3 is past the end of the array (which contains 1 element) [-Warray-bounds]
return (set1->sig[3] == set2->sig[3]) &&
vim +/DRV_NAME +849 include/linux/device.h
826
827 /*
828 * Note: this routine expects that the state of @dev->mutex is stable
829 * from entry to exit. There is no support for changing lockdep
830 * validation classes, only enabling and disabling validation.
831 */
832 static inline void device_set_lock_class(struct device *dev, int lock_class)
833 {
834 /*
835 * Allow for setting or clearing the lock class while the
836 * device_lock() is held, in which case the paired nested lock
837 * might need to be acquired or released now to accommodate the
838 * next device_unlock().
839 */
840 if (dev->lock_class < 0 && lock_class >= 0) {
841 /* Enabling lockdep validation... */
842 if (mutex_is_locked(&dev->mutex))
843 mutex_lock_nested(&dev->lockdep_mutex, lock_class);
844 } else if (dev->lock_class >= 0 && lock_class < 0) {
845 /* Disabling lockdep validation... */
846 if (mutex_is_locked(&dev->mutex))
847 mutex_unlock(&dev->lockdep_mutex);
848 } else {
> 849 dev_warn(dev,
850 "%s: failed to change lock_class from: %d to %d\n",
851 __func__, dev->lock_class, lock_class);
852 return;
853 }
854 dev->lock_class = lock_class;
855 }
856 #else /* !CONFIG_PROVE_LOCKING */
857 static inline void device_lockdep_init(struct device *dev)
858 {
859 lockdep_set_novalidate_class(&dev->mutex);
860 }
861
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-09 6:24 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=202204091427.VqNnQI8Y-lkp@intel.com \
--to=lkp@intel.com \
--cc=alison.schofield@intel.com \
--cc=ben.widawsky@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=vishal.l.verma@intel.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
all inboxes | Powered by JetHome®