* [dm-devel] [device-mapper-dm:for-next 2/4] drivers/md/persistent-data/dm-extent-allocator.c:530:24: error: expected '; ' after expression
@ 2023-09-15 2:54 ` kernel test robot
0 siblings, 0 replies; 4+ messages in thread
From: kernel test robot @ 2023-09-15 2:54 UTC (permalink / raw)
To: Joe Thornber; +Cc: dm-devel, llvm, Mike Snitzer, oe-kbuild-all
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
^ permalink raw reply [flat|nested] 4+ messages in thread* [device-mapper-dm:for-next 2/4] drivers/md/persistent-data/dm-extent-allocator.c:530:24: error: expected ';' after expression
@ 2023-09-15 2:54 ` kernel test robot
0 siblings, 0 replies; 4+ messages in thread
From: kernel test robot @ 2023-09-15 2:54 UTC (permalink / raw)
To: Joe Thornber; +Cc: llvm, oe-kbuild-all, dm-devel, Mike Snitzer
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
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [dm-devel] [device-mapper-dm:for-next 2/4] drivers/md/persistent-data/dm-extent-allocator.c:530:24: error: expected '; ' after expression
2023-09-15 2:54 ` [device-mapper-dm:for-next 2/4] drivers/md/persistent-data/dm-extent-allocator.c:530:24: error: expected ';' " kernel test robot
@ 2023-09-15 3:34 ` Mike Snitzer
-1 siblings, 0 replies; 4+ messages in thread
From: Mike Snitzer @ 2023-09-15 3:34 UTC (permalink / raw)
To: kernel test robot; +Cc: Joe Thornber, llvm, dm-devel, oe-kbuild-all
On Thu, Sep 14 2023 at 10:54P -0400,
kernel test robot <lkp@intel.com> wrote:
> 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.
These were my fault.. Fixed, sorry about the noise.
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-09-15 3:34 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-09-15 2:54 [dm-devel] [device-mapper-dm:for-next 2/4] drivers/md/persistent-data/dm-extent-allocator.c:530:24: error: expected '; ' after expression kernel test robot
2023-09-15 2:54 ` [device-mapper-dm:for-next 2/4] drivers/md/persistent-data/dm-extent-allocator.c:530:24: error: expected ';' " kernel test robot
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 '; ' " Mike Snitzer
2023-09-15 3:34 ` Mike Snitzer
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.