linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: kbuild test robot <lkp@intel.com>,
	kbuild-all@01.org, linux-btrfs@vger.kernel.org, dsterba@suse.cz
Subject: Re: [kbuild-all] [PATCH] btrfs: Use btrfs_space_info_used instead of opencoding it
Date: Fri, 16 Jun 2017 16:05:25 +0800	[thread overview]
Message-ID: <20170616080525.GA23108@yexl-desktop> (raw)
In-Reply-To: <bf36f06d-c8fd-b54f-5027-3f3940618906@suse.com>

On 06/15, Nikolay Borisov wrote:
>
>
>On 15.06.2017 04:17, kbuild test robot wrote:
>> Hi Nikolay,
>> 
>> [auto build test ERROR on v4.9-rc8]
>> [cannot apply to btrfs/next kdave/for-next next-20170614]
>> [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/Nikolay-Borisov/btrfs-Use-btrfs_space_info_used-instead-of-opencoding-it/20170615-084940
>> config: x86_64-randconfig-x012-201724 (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=x86_64 
>> 
>> All errors (new ones prefixed by >>):
>> 
>>    fs/btrfs/extent-tree.c: In function 'btrfs_calc_reclaim_metadata_size':
>>>> fs/btrfs/extent-tree.c:4918:9: error: implicit declaration of function 'btrfs_space_info_used' [-Werror=implicit-function-declaration]
>>      used = btrfs_space_info_used(space_info, true);
>>             ^~~~~~~~~~~~~~~~~~~~~
>>    cc1: some warnings being treated as errors
>
>This patch builds cleanly on latest linux master and it's based off that
>tree. I don't see why it's being applied to 4.9-rc8.
>

Sorry it's caused by one bug in 0day, now we've fixed it in latest code.
Thanks for your information.

Thanks,
Xiaolong

>
>> 
>> vim +/btrfs_space_info_used +4918 fs/btrfs/extent-tree.c
>> 
>>   4912	
>>   4913		to_reclaim = min_t(u64, num_online_cpus() * SZ_1M, SZ_16M);
>>   4914		if (can_overcommit(root, space_info, to_reclaim,
>>   4915				   BTRFS_RESERVE_FLUSH_ALL))
>>   4916			return 0;
>>   4917	
>>> 4918		used = btrfs_space_info_used(space_info, true);
>>   4919	
>>   4920		if (can_overcommit(root, space_info, SZ_1M, BTRFS_RESERVE_FLUSH_ALL))
>>   4921			expected = div_factor_fine(space_info->total_bytes, 95);
>> 
>> ---
>> 0-DAY kernel test infrastructure                Open Source Technology Center
>> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
>> 
>_______________________________________________
>kbuild-all mailing list
>kbuild-all@lists.01.org
>https://lists.01.org/mailman/listinfo/kbuild-all

  reply	other threads:[~2017-06-16  8:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14  8:35 [PATCH] btrfs: Use btrfs_space_info_used instead of opencoding it Nikolay Borisov
2017-06-15  1:17 ` kbuild test robot
2017-06-15  6:32   ` Nikolay Borisov
2017-06-16  8:05     ` Ye Xiaolong [this message]
2017-06-15 15:36 ` David Sterba

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=20170616080525.GA23108@yexl-desktop \
    --to=xiaolong.ye@intel.com \
    --cc=dsterba@suse.cz \
    --cc=kbuild-all@01.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=nborisov@suse.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;
as well as URLs for NNTP newsgroup(s).