From: kbuild test robot <lkp@intel.com>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: kbuild-all@01.org, Linux-MM <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org, Dan Streetman <ddstreet@ieee.org>,
Andrew Morton <akpm@linux-foundation.org>,
Oleksiy.Avramchenko@sony.com
Subject: Re: [PATCH] z3fold: use per-cpu unbuddied lists
Date: Wed, 2 Aug 2017 21:50:42 +0800 [thread overview]
Message-ID: <201708022101.VfFg8fxz%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170802122505.e41d5c778a873375bcb0cc19@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1880 bytes --]
Hi Vitaly,
[auto build test ERROR on mmotm/master]
[also build test ERROR on v4.13-rc3 next-20170802]
[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/Vitaly-Wool/z3fold-use-per-cpu-unbuddied-lists/20170802-211153
base: git://git.cmpxchg.org/linux-mmotm.git master
config: i386-randconfig-x019-201731 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
mm/z3fold.c: In function 'free_pages_work':
>> mm/z3fold.c:310:3: error: implicit declaration of function 'cond_resched' [-Werror=implicit-function-declaration]
cond_resched();
^~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/cond_resched +310 mm/z3fold.c
292
293 static void free_pages_work(struct work_struct *w)
294 {
295 struct z3fold_pool *pool = container_of(w, struct z3fold_pool, work);
296
297 spin_lock(&pool->stale_lock);
298 while (!list_empty(&pool->stale)) {
299 struct z3fold_header *zhdr = list_first_entry(&pool->stale,
300 struct z3fold_header, buddy);
301 struct page *page = virt_to_page(zhdr);
302
303 list_del(&zhdr->buddy);
304 if (WARN_ON(!test_bit(PAGE_STALE, &page->private)))
305 continue;
306 clear_bit(NEEDS_COMPACTING, &page->private);
307 spin_unlock(&pool->stale_lock);
308 cancel_work_sync(&zhdr->work);
309 free_z3fold_page(page);
> 310 cond_resched();
311 spin_lock(&pool->stale_lock);
312 }
313 spin_unlock(&pool->stale_lock);
314 }
315
---
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: 27394 bytes --]
next prev parent reply other threads:[~2017-08-02 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 10:25 Vitaly Wool
2017-08-02 13:50 ` kbuild test robot [this message]
2017-08-02 23:07 ` Andrew Morton
2017-08-02 23:49 ` Vitaly Wool
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=201708022101.VfFg8fxz%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=Oleksiy.Avramchenko@sony.com \
--cc=akpm@linux-foundation.org \
--cc=ddstreet@ieee.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vitalywool@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