From: kbuild test robot <lkp@intel.com>
To: Josef Bacik <jbacik@fb.com>
Cc: kbuild-all@01.org, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, kernel-team@fb.com, jack@suse.com,
viro@zeniv.linux.org.uk, dchinner@redhat.com, hch@lst.de
Subject: Re: [PATCH 1/2] remove mapping from balance_dirty_pages*()
Date: Wed, 10 Aug 2016 03:30:30 +0800 [thread overview]
Message-ID: <201608100334.lxYJQkr2%fengguang.wu@intel.com> (raw)
In-Reply-To: <1470769707-26079-2-git-send-email-jbacik@fb.com>
[-- Attachment #1: Type: text/plain, Size: 2431 bytes --]
Hi Josef,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.8-rc1 next-20160809]
[cannot apply to linux/master]
[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/Josef-Bacik/Provide-accounting-for-dirty-metadata/20160810-031219
config: x86_64-randconfig-x019-201632 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
In file included from include/linux/linkage.h:4:0,
from include/linux/kernel.h:6,
from mm/page-writeback.c:14:
mm/page-writeback.c: In function 'balance_dirty_pages_ratelimited':
mm/page-writeback.c:1873:6: error: implicit declaration of function 'bdi_cgwb_enabled' [-Werror=implicit-function-declaration]
if (bdi_cgwb_enabled(bdi, sb))
^
include/linux/compiler.h:149:30: note: in definition of macro '__trace_if'
if (__builtin_constant_p(!!(cond)) ? !!(cond) : \
^~~~
>> mm/page-writeback.c:1873:2: note: in expansion of macro 'if'
if (bdi_cgwb_enabled(bdi, sb))
^~
cc1: some warnings being treated as errors
vim +/if +1873 mm/page-writeback.c
1857 *
1858 * On really big machines, get_writeback_state is expensive, so try to avoid
1859 * calling it too often (ratelimiting). But once we're over the dirty memory
1860 * limit we decrease the ratelimiting by a lot, to prevent individual processes
1861 * from overshooting the limit by (ratelimit_pages) each.
1862 */
1863 void balance_dirty_pages_ratelimited(struct backing_dev_info *bdi,
1864 struct super_block *sb)
1865 {
1866 struct bdi_writeback *wb = NULL;
1867 int ratelimit;
1868 int *p;
1869
1870 if (!bdi_cap_account_dirty(bdi))
1871 return;
1872
> 1873 if (bdi_cgwb_enabled(bdi, sb))
1874 wb = wb_get_create_current(bdi, GFP_KERNEL);
1875 if (!wb)
1876 wb = &bdi->wb;
1877
1878 ratelimit = current->nr_dirtied_pause;
1879 if (wb->dirty_exceeded)
1880 ratelimit = min(ratelimit, 32 >> (PAGE_SHIFT - 10));
1881
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 26211 bytes --]
next prev parent reply other threads:[~2016-08-09 19:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 19:08 [PATCH 0/2][RFC] Provide accounting for dirty metadata Josef Bacik
2016-08-09 19:08 ` [PATCH 1/2] remove mapping from balance_dirty_pages*() Josef Bacik
2016-08-09 19:30 ` kbuild test robot [this message]
2016-08-09 19:32 ` kbuild test robot
2016-08-09 20:12 ` kbuild test robot
2016-08-09 20:50 ` kbuild test robot
2016-08-10 8:27 ` Jan Kara
2016-08-10 8:29 ` Jan Kara
2016-08-10 19:56 ` Tejun Heo
2016-08-09 19:08 ` [PATCH 2/2] writeback: allow for dirty metadata accounting Josef Bacik
2016-08-10 10:09 ` Jan Kara
2016-08-10 14:05 ` Josef Bacik
2016-08-10 20:12 ` Tejun Heo
2016-08-10 21:16 ` Josef Bacik
2016-08-10 21:39 ` Tejun Heo
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=201608100334.lxYJQkr2%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dchinner@redhat.com \
--cc=hch@lst.de \
--cc=jack@suse.com \
--cc=jbacik@fb.com \
--cc=kbuild-all@01.org \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).