mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Amol Grover <frextrite@gmail.com>
Cc: kbuild-all@lists.01.org, Christoph Hellwig <hch@lst.de>,
	Sagi Grimberg <sagi@grimberg.me>,
	Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-kernel-mentees@lists.linuxfoundation.org,
	Joel Fernandes <joel@joelfernandes.org>,
	Madhuparna Bhowmik <madhuparnabhowmik04@gmail.com>,
	"Paul E . McKenney" <paulmck@kernel.org>,
	Amol Grover <frextrite@gmail.com>
Subject: Re: [PATCH v2] drivers: nvme: target: core: Pass lockdep expression to RCU lists
Date: Sat, 18 Jan 2020 19:06:01 +0800	[thread overview]
Message-ID: <202001181921.9Sj3wG9D%lkp@intel.com> (raw)
In-Reply-To: <20200110172343.17796-1-frextrite@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4022 bytes --]

Hi Amol,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on hch-configfs/for-next]
[also build test ERROR on linux/master linus/master v5.5-rc6 next-20200117]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Amol-Grover/drivers-nvme-target-core-Pass-lockdep-expression-to-RCU-lists/20200111-084508
base:   git://git.infradead.org/users/hch/configfs.git for-next
config: i386-randconfig-e001-20200118 (attached as .config)
compiler: gcc-7 (Debian 7.5.0-3) 7.5.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   In file included from include/linux/rbtree.h:22:0,
                    from include/linux/mm_types.h:10,
                    from include/linux/mmzone.h:21,
                    from include/linux/gfp.h:6,
                    from include/linux/umh.h:4,
                    from include/linux/kmod.h:9,
                    from include/linux/module.h:13,
                    from drivers/nvme/target/core.c:7:
   drivers/nvme/target/core.c: In function 'nvmet_setup_p2p_ns_map':
>> drivers/nvme/target/core.c:1179:22: error: 'subsys' undeclared (first use in this function); did you mean 'to_subsys'?
        lockdep_is_held(&subsys->lock))
                         ^
   include/linux/rcupdate.h:263:52: note: in definition of macro 'RCU_LOCKDEP_WARN'
      if (debug_lockdep_rcu_enabled() && !__warned && (c)) { \
                                                       ^
   include/linux/rculist.h:371:7: note: in expansion of macro '__list_check_rcu'
     for (__list_check_rcu(dummy, ## cond, 0),   \
          ^~~~~~~~~~~~~~~~
   include/linux/rculist.h:371:34: note: in expansion of macro 'lockdep_is_held'
     for (__list_check_rcu(dummy, ## cond, 0),   \
                                     ^~~~
   drivers/nvme/target/core.c:1178:2: note: in expansion of macro 'list_for_each_entry_rcu'
     list_for_each_entry_rcu(ns, &ctrl->subsys->namespaces, dev_link,
     ^~~~~~~~~~~~~~~~~~~~~~~
   drivers/nvme/target/core.c:1179:22: note: each undeclared identifier is reported only once for each function it appears in
        lockdep_is_held(&subsys->lock))
                         ^
   include/linux/rcupdate.h:263:52: note: in definition of macro 'RCU_LOCKDEP_WARN'
      if (debug_lockdep_rcu_enabled() && !__warned && (c)) { \
                                                       ^
   include/linux/rculist.h:371:7: note: in expansion of macro '__list_check_rcu'
     for (__list_check_rcu(dummy, ## cond, 0),   \
          ^~~~~~~~~~~~~~~~
   include/linux/rculist.h:371:34: note: in expansion of macro 'lockdep_is_held'
     for (__list_check_rcu(dummy, ## cond, 0),   \
                                     ^~~~
   drivers/nvme/target/core.c:1178:2: note: in expansion of macro 'list_for_each_entry_rcu'
     list_for_each_entry_rcu(ns, &ctrl->subsys->namespaces, dev_link,
     ^~~~~~~~~~~~~~~~~~~~~~~

vim +1179 drivers/nvme/target/core.c

  1164	
  1165	/*
  1166	 * Note: ctrl->subsys->lock should be held when calling this function
  1167	 */
  1168	static void nvmet_setup_p2p_ns_map(struct nvmet_ctrl *ctrl,
  1169			struct nvmet_req *req)
  1170	{
  1171		struct nvmet_ns *ns;
  1172	
  1173		if (!req->p2p_client)
  1174			return;
  1175	
  1176		ctrl->p2p_client = get_device(req->p2p_client);
  1177	
  1178		list_for_each_entry_rcu(ns, &ctrl->subsys->namespaces, dev_link,
> 1179					lockdep_is_held(&subsys->lock))
  1180			nvmet_p2pmem_ns_add_p2p(ctrl, ns);
  1181	}
  1182	

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32548 bytes --]

      parent reply	other threads:[~2020-01-18 11:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 17:23 Amol Grover
2020-01-11  5:43 ` kbuild test robot
2020-01-18 11:06 ` kbuild test robot [this message]

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=202001181921.9Sj3wG9D%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=chaitanya.kulkarni@wdc.com \
    --cc=frextrite@gmail.com \
    --cc=hch@lst.de \
    --cc=joel@joelfernandes.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=madhuparnabhowmik04@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=sagi@grimberg.me \
    /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®