Linux virtualization list
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Wei Wang <wei.w.wang@intel.com>
Cc: yang.zhang.wz@gmail.com, kvm@vger.kernel.org, mst@redhat.com,
	penguin-kernel@I-love.SAKURA.ne.jp, liliang.opensource@gmail.com,
	qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org,
	linux-mm@kvack.org, aarcange@redhat.com,
	virtio-dev@lists.oasis-open.org, mawilcox@microsoft.com,
	willy@infradead.org, quan.xu@aliyun.com, nilal@redhat.com,
	riel@redhat.com, cornelia.huck@de.ibm.com, mhocko@kernel.org,
	linux-kernel@vger.kernel.org, kbuild-all@01.org,
	amit.shah@redhat.com, pbonzini@redhat.com,
	akpm@linux-foundation.org, mgorman@techsingularity.net
Subject: Re: [PATCH v19 2/7] xbitmap: potential improvement
Date: Fri, 15 Dec 2017 11:07:41 +0800	[thread overview]
Message-ID: <201712151043.losrwclY%fengguang.wu@intel.com> (raw)
In-Reply-To: <1513079759-14169-3-git-send-email-wei.w.wang@intel.com>

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

Hi Wei,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v4.15-rc3 next-20171214]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Wei-Wang/Virtio-balloon-Enhancement/20171215-100525
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

Note: the linux-review/Wei-Wang/Virtio-balloon-Enhancement/20171215-100525 HEAD 607ddba072bf7f9c9cbacedaccad7c42c5c7149c builds fine.
      It only hurts bisectibility.

All errors (new ones prefixed by >>):

>> lib/xbitmap.c:80:6: error: conflicting types for 'xb_clear_bit'
    void xb_clear_bit(struct xb *xb, unsigned long bit)
         ^~~~~~~~~~~~
   In file included from lib/xbitmap.c:2:0:
   include/linux/xbitmap.h:37:5: note: previous declaration of 'xb_clear_bit' was here
    int xb_clear_bit(struct xb *xb, unsigned long bit);
        ^~~~~~~~~~~~

vim +/xb_clear_bit +80 lib/xbitmap.c

    71	
    72	/**
    73	 * xb_clear_bit - clear a bit in the xbitmap
    74	 * @xb: the xbitmap tree used to record the bit
    75	 * @bit: index of the bit to clear
    76	 *
    77	 * This function is used to clear a bit in the xbitmap. If all the bits of the
    78	 * bitmap are 0, the bitmap will be freed.
    79	 */
  > 80	void xb_clear_bit(struct xb *xb, unsigned long bit)
    81	{
    82		unsigned long index = bit / IDA_BITMAP_BITS;
    83		struct radix_tree_root *root = &xb->xbrt;
    84		struct radix_tree_node *node;
    85		void **slot;
    86		struct ida_bitmap *bitmap;
    87		unsigned long ebit;
    88	
    89		bit %= IDA_BITMAP_BITS;
    90		ebit = bit + 2;
    91	
    92		bitmap = __radix_tree_lookup(root, index, &node, &slot);
    93		if (radix_tree_exception(bitmap)) {
    94			unsigned long tmp = (unsigned long)bitmap;
    95	
    96			if (ebit >= BITS_PER_LONG)
    97				return;
    98			tmp &= ~(1UL << ebit);
    99			if (tmp == RADIX_TREE_EXCEPTIONAL_ENTRY)
   100				__radix_tree_delete(root, node, slot);
   101			else
   102				rcu_assign_pointer(*slot, (void *)tmp);
   103			return;
   104		}
   105	
   106		if (!bitmap)
   107			return;
   108	
   109		__clear_bit(bit, bitmap->bitmap);
   110		if (bitmap_empty(bitmap->bitmap, IDA_BITMAP_BITS)) {
   111			kfree(bitmap);
   112			__radix_tree_delete(root, node, slot);
   113		}
   114	}
   115	EXPORT_SYMBOL(xb_clear_bit);
   116	

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

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

[-- Attachment #3: Type: text/plain, Size: 183 bytes --]

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

       reply	other threads:[~2017-12-15  3:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1513079759-14169-3-git-send-email-wei.w.wang@intel.com>
2017-12-15  3:07 ` kbuild test robot [this message]
     [not found] <1513079759-14169-1-git-send-email-wei.w.wang@intel.com>
2017-12-12 11:55 ` [PATCH v19 2/7] xbitmap: potential improvement Wei Wang

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=201712151043.losrwclY%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=amit.shah@redhat.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=kbuild-all@01.org \
    --cc=kvm@vger.kernel.org \
    --cc=liliang.opensource@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mawilcox@microsoft.com \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@kernel.org \
    --cc=mst@redhat.com \
    --cc=nilal@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=qemu-devel@nongnu.org \
    --cc=quan.xu@aliyun.com \
    --cc=riel@redhat.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=wei.w.wang@intel.com \
    --cc=willy@infradead.org \
    --cc=yang.zhang.wz@gmail.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