From: Dilger, Andreas <andreas.dilger@intel.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH] staging: lustre: cl_lock: Remove cl_lock_lockdep_init wrapper
Date: Fri, 13 Nov 2015 00:59:01 +0000 [thread overview]
Message-ID: <D26A8399.11A59C%andreas.dilger@intel.com> (raw)
In-Reply-To: <CAKHNQQHLwsfv6OKOci4g4405_vcFgy7GNcUAWX0aDAS+GFU6gw@mail.gmail.com>
On 2015/11/11, 10:21, "lustre-devel on behalf of Shivani Bhardwaj"
<lustre-devel-bounces at lists.lustre.org on behalf of shivanib134@gmail.com>
wrote:
>On Wed, Nov 11, 2015 at 4:24 PM, kbuild test robot <lkp@intel.com> wrote:
>> Hi Shivani,
>>
>> [auto build test ERROR on staging/staging-testing]
>> [also build test ERROR on v4.3 next-20151111]
>>
>> url:
>>https://github.com/0day-ci/linux/commits/Shivani-Bhardwaj/staging-lustre-
>>cl_lock-Remove-cl_lock_lockdep_init-wrapper/20151111-182452
>> config: m68k-allyesconfig (attached as .config)
>> reproduce:
>> wget
>>https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin
>>/make.cross -O ~/bin/make.cross
>> chmod +x ~/bin/make.cross
>> # save the attached .config to linux build tree
>> make.cross ARCH=m68k
>>
>> All errors (new ones prefixed by >>):
>>
>> In file included from include/linux/spinlock_types.h:18:0,
>> from include/linux/spinlock.h:81,
>> from include/linux/mmzone.h:7,
>> from include/linux/gfp.h:5,
>> from include/linux/slab.h:14,
>> from
>>drivers/staging/lustre/lustre/obdclass/../include/obd_support.h:40,
>> from
>>drivers/staging/lustre/lustre/obdclass/../include/obd_class.h:39,
>> from
>>drivers/staging/lustre/lustre/obdclass/cl_lock.c:43:
>> drivers/staging/lustre/lustre/obdclass/cl_lock.c: In function
>>'cl_lock_alloc':
>>>> drivers/staging/lustre/lustre/obdclass/cl_lock.c:379:37: error:
>>>>'cl_lock_key' undeclared (first use in this function)
>> lockdep_set_class_and_name(lock, &cl_lock_key, "EXT");
>> ^
>> include/linux/lockdep.h:401:15: note: in definition of macro
>>'lockdep_set_class_and_name'
>> do { (void)(key); (void)(name); } while (0)
>> ^
>> drivers/staging/lustre/lustre/obdclass/cl_lock.c:379:37: note: each
>>undeclared identifier is reported only once for each function it appears
>>in
>> lockdep_set_class_and_name(lock, &cl_lock_key, "EXT");
>> ^
>> include/linux/lockdep.h:401:15: note: in definition of macro
>>'lockdep_set_class_and_name'
>> do { (void)(key); (void)(name); } while (0)
>> ^
>> drivers/staging/lustre/lustre/obdclass/cl_lock.c: At top level:
>> drivers/staging/lustre/lustre/obdclass/cl_lock.c:166:13: warning:
>>'cl_lock_lockdep_init' defined but not used [-Wunused-function]
>> static void cl_lock_lockdep_init(struct cl_lock *lock)
>> ^
>>
>> vim +/cl_lock_key +379 drivers/staging/lustre/lustre/obdclass/cl_lock.c
>>
>> 373 lockdep_set_class(&lock->cll_guard,
>>&cl_lock_guard_class);
>> 374 init_waitqueue_head(&lock->cll_wq);
>> 375 head = obj->co_lu.lo_header;
>> 376 CS_LOCKSTATE_INC(obj, CLS_NEW);
>> 377 CS_LOCK_INC(obj, total);
>> 378 CS_LOCK_INC(obj, create);
>> > 379 lockdep_set_class_and_name(lock, &cl_lock_key,
>>"EXT");
>> 380 list_for_each_entry(obj, &head->loh_layers,
>> 381 co_lu.lo_linkage) {
>> 382 int err;
>>
>> ---
>> 0-DAY kernel test infrastructure Open Source Technology
>>Center
>> https://lists.01.org/pipermail/kbuild-all Intel
>>Corporation
>
>Hi all,
>
>I'm not getting any of these errors at compilation. I've checked
>thrice. Could you please tell what am I doing wrong so that I can
>avoid introducing errors in future patches?
You need to have CONFIG_LOCKDEP_SUPPORT=y in your kernel .config file.
Cheers, Andreas
--
Andreas Dilger
Lustre Principal Engineer
Intel High Performance Data Division
WARNING: multiple messages have this Message-ID (diff)
From: "Dilger, Andreas" <andreas.dilger@intel.com>
To: Shivani Bhardwaj <shivanib134@gmail.com>, lkp <lkp@intel.com>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Greg KH <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Drokin, Oleg" <oleg.drokin@intel.com>,
"kbuild-all@01.org" <kbuild-all@01.org>,
"lustre-devel@lists.lustre.org" <lustre-devel@lists.lustre.org>
Subject: Re: [lustre-devel] [PATCH] staging: lustre: cl_lock: Remove cl_lock_lockdep_init wrapper
Date: Fri, 13 Nov 2015 00:59:01 +0000 [thread overview]
Message-ID: <D26A8399.11A59C%andreas.dilger@intel.com> (raw)
In-Reply-To: <CAKHNQQHLwsfv6OKOci4g4405_vcFgy7GNcUAWX0aDAS+GFU6gw@mail.gmail.com>
On 2015/11/11, 10:21, "lustre-devel on behalf of Shivani Bhardwaj"
<lustre-devel-bounces@lists.lustre.org on behalf of shivanib134@gmail.com>
wrote:
>On Wed, Nov 11, 2015 at 4:24 PM, kbuild test robot <lkp@intel.com> wrote:
>> Hi Shivani,
>>
>> [auto build test ERROR on staging/staging-testing]
>> [also build test ERROR on v4.3 next-20151111]
>>
>> url:
>>https://github.com/0day-ci/linux/commits/Shivani-Bhardwaj/staging-lustre-
>>cl_lock-Remove-cl_lock_lockdep_init-wrapper/20151111-182452
>> config: m68k-allyesconfig (attached as .config)
>> reproduce:
>> wget
>>https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin
>>/make.cross -O ~/bin/make.cross
>> chmod +x ~/bin/make.cross
>> # save the attached .config to linux build tree
>> make.cross ARCH=m68k
>>
>> All errors (new ones prefixed by >>):
>>
>> In file included from include/linux/spinlock_types.h:18:0,
>> from include/linux/spinlock.h:81,
>> from include/linux/mmzone.h:7,
>> from include/linux/gfp.h:5,
>> from include/linux/slab.h:14,
>> from
>>drivers/staging/lustre/lustre/obdclass/../include/obd_support.h:40,
>> from
>>drivers/staging/lustre/lustre/obdclass/../include/obd_class.h:39,
>> from
>>drivers/staging/lustre/lustre/obdclass/cl_lock.c:43:
>> drivers/staging/lustre/lustre/obdclass/cl_lock.c: In function
>>'cl_lock_alloc':
>>>> drivers/staging/lustre/lustre/obdclass/cl_lock.c:379:37: error:
>>>>'cl_lock_key' undeclared (first use in this function)
>> lockdep_set_class_and_name(lock, &cl_lock_key, "EXT");
>> ^
>> include/linux/lockdep.h:401:15: note: in definition of macro
>>'lockdep_set_class_and_name'
>> do { (void)(key); (void)(name); } while (0)
>> ^
>> drivers/staging/lustre/lustre/obdclass/cl_lock.c:379:37: note: each
>>undeclared identifier is reported only once for each function it appears
>>in
>> lockdep_set_class_and_name(lock, &cl_lock_key, "EXT");
>> ^
>> include/linux/lockdep.h:401:15: note: in definition of macro
>>'lockdep_set_class_and_name'
>> do { (void)(key); (void)(name); } while (0)
>> ^
>> drivers/staging/lustre/lustre/obdclass/cl_lock.c: At top level:
>> drivers/staging/lustre/lustre/obdclass/cl_lock.c:166:13: warning:
>>'cl_lock_lockdep_init' defined but not used [-Wunused-function]
>> static void cl_lock_lockdep_init(struct cl_lock *lock)
>> ^
>>
>> vim +/cl_lock_key +379 drivers/staging/lustre/lustre/obdclass/cl_lock.c
>>
>> 373 lockdep_set_class(&lock->cll_guard,
>>&cl_lock_guard_class);
>> 374 init_waitqueue_head(&lock->cll_wq);
>> 375 head = obj->co_lu.lo_header;
>> 376 CS_LOCKSTATE_INC(obj, CLS_NEW);
>> 377 CS_LOCK_INC(obj, total);
>> 378 CS_LOCK_INC(obj, create);
>> > 379 lockdep_set_class_and_name(lock, &cl_lock_key,
>>"EXT");
>> 380 list_for_each_entry(obj, &head->loh_layers,
>> 381 co_lu.lo_linkage) {
>> 382 int err;
>>
>> ---
>> 0-DAY kernel test infrastructure Open Source Technology
>>Center
>> https://lists.01.org/pipermail/kbuild-all Intel
>>Corporation
>
>Hi all,
>
>I'm not getting any of these errors at compilation. I've checked
>thrice. Could you please tell what am I doing wrong so that I can
>avoid introducing errors in future patches?
You need to have CONFIG_LOCKDEP_SUPPORT=y in your kernel .config file.
Cheers, Andreas
--
Andreas Dilger
Lustre Principal Engineer
Intel High Performance Data Division
next prev parent reply other threads:[~2015-11-13 0:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 10:21 [lustre-devel] [PATCH] staging: lustre: cl_lock: Remove cl_lock_lockdep_init wrapper Shivani Bhardwaj
2015-11-11 10:21 ` Shivani Bhardwaj
2015-11-11 10:54 ` [lustre-devel] " kbuild test robot
2015-11-11 10:54 ` kbuild test robot
2015-11-11 17:21 ` [lustre-devel] " Shivani Bhardwaj
2015-11-11 17:21 ` Shivani Bhardwaj
2015-11-11 17:31 ` [lustre-devel] " Greg KH
2015-11-11 17:31 ` Greg KH
2015-11-11 17:33 ` [lustre-devel] " Shivani Bhardwaj
2015-11-11 17:33 ` Shivani Bhardwaj
2015-11-13 13:03 ` [lustre-devel] " Sudip Mukherjee
2015-11-13 13:03 ` Sudip Mukherjee
2015-11-13 13:06 ` [lustre-devel] " Shivani Bhardwaj
2015-11-13 13:06 ` Shivani Bhardwaj
2015-11-13 0:59 ` Dilger, Andreas [this message]
2015-11-13 0:59 ` [lustre-devel] " Dilger, Andreas
2015-11-13 5:14 ` Shivani Bhardwaj
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=D26A8399.11A59C%andreas.dilger@intel.com \
--to=andreas.dilger@intel.com \
--cc=lustre-devel@lists.lustre.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 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.