Linux Device Mapper development
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Joe Thornber <ejt@redhat.com>
Cc: dm-devel@redhat.com, llvm@lists.linux.dev,
	Mike Snitzer <snitzer@kernel.org>,
	oe-kbuild-all@lists.linux.dev
Subject: [dm-devel] [device-mapper-dm:for-next 2/4] drivers/md/persistent-data/dm-extent-allocator.c:530:24: error: expected '; ' after expression
Date: Fri, 15 Sep 2023 10:54:53 +0800	[thread overview]
Message-ID: <202309151023.QPBCNoCN-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
head:   edcabec81f12dfc9b86b05084bba3232efdc5e4e
commit: 59d814674dd66fc64ba229605174bfe0b8e566d5 [2/4] dm persistent data: Introduce extent allocator
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20230915/202309151023.QPBCNoCN-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230915/202309151023.QPBCNoCN-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/202309151023.QPBCNoCN-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/md/persistent-data/dm-extent-allocator.c:530:24: error: expected ';' after expression
           spin_unlock(&ea->lock)
                                 ^
                                 ;
   drivers/md/persistent-data/dm-extent-allocator.c:544:24: error: expected ';' after expression
           spin_unlock(&ea->lock)
                                 ^
                                 ;
   2 errors generated.


vim +530 drivers/md/persistent-data/dm-extent-allocator.c

   511	
   512	void dm_alloc_context_get(struct dm_extent_allocator *ea,
   513				  struct dm_alloc_context *ac)
   514	{
   515		spin_lock(&ea->lock);
   516		ac->ea = ea;
   517	
   518		ea->nr_allocation_contexts++;
   519	
   520		/*
   521		 * We try and maintain a couple of nodes per alloc context to avoid sharing.
   522		 * If allocation fails it's no big deal; we'll just get more fragmentation.
   523		 */
   524		if (ea->nr_preallocated_nodes < ea->nr_allocation_contexts * 2)
   525			__prealloc_nodes(ea, 2, GFP_NOIO);
   526	
   527		list_add(&ac->list, &ea->allocation_contexts);
   528		INIT_LIST_HEAD(&ac->holders_list);
   529		ac->leaf = NULL;
 > 530		spin_unlock(&ea->lock)
   531	}
   532	EXPORT_SYMBOL_GPL(dm_alloc_context_get);
   533	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel


             reply	other threads:[~2023-09-15  2:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15  2:54 kernel test robot [this message]
2023-09-15  3:34 ` [dm-devel] [device-mapper-dm:for-next 2/4] drivers/md/persistent-data/dm-extent-allocator.c:530:24: error: expected '; ' after expression Mike Snitzer

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=202309151023.QPBCNoCN-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dm-devel@redhat.com \
    --cc=ejt@redhat.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=snitzer@kernel.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