public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ioannis Angelakopoulos <iangelak@fb.com>,
	linux-btrfs@vger.kernel.org, kernel-team@fb.com
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH 1/2] btrfs: Add the capability of getting commit stats in BTRFS
Date: Sat, 11 Jun 2022 20:55:35 +0800	[thread overview]
Message-ID: <202206112045.UQwxPCB0-lkp@intel.com> (raw)
In-Reply-To: <20220610205406.301397-2-iangelak@fb.com>

Hi Ioannis,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on kdave/for-next]
[also build test ERROR on v5.19-rc1 next-20220610]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/intel-lab-lkp/linux/commits/Ioannis-Angelakopoulos/btrfs-Expose-BTRFS-commit-stats-through-sysfs/20220611-045738
base:   https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
config: microblaze-randconfig-r015-20220611 (https://download.01.org/0day-ci/archive/20220611/202206112045.UQwxPCB0-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 11.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/intel-lab-lkp/linux/commit/8f66d4d3d43f1502549101630cdc1291093b7596
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review Ioannis-Angelakopoulos/btrfs-Expose-BTRFS-commit-stats-through-sysfs/20220611-045738
        git checkout 8f66d4d3d43f1502549101630cdc1291093b7596
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=microblaze SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   microblaze-linux-ld: fs/btrfs/transaction.o: in function `update_commit_stats':
>> fs/btrfs/transaction.c:2094: undefined reference to `__divdi3'


vim +2094 fs/btrfs/transaction.c

  2087	
  2088	static void update_commit_stats(struct btrfs_fs_info *fs_info,
  2089									ktime_t interval)
  2090	{
  2091		/* Increase the successful commits counter */
  2092		fs_info->commit_stats->commit_counter += 1;
  2093		/* Update the last commit duration */
> 2094		fs_info->commit_stats->last_commit_dur = interval / 1000000;
  2095		/* Update the maximum commit duration */
  2096		fs_info->commit_stats->max_commit_dur =
  2097					fs_info->commit_stats->max_commit_dur >	interval / 1000000 ?
  2098					fs_info->commit_stats->max_commit_dur :	interval / 1000000;
  2099		/* Update the total commit duration */
  2100		fs_info->commit_stats->total_commit_dur += interval / 1000000;
  2101	}
  2102	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

  parent reply	other threads:[~2022-06-11 12:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 20:54 [PATCH 0/2] btrfs: Expose BTRFS commit stats through sysfs Ioannis Angelakopoulos
2022-06-10 20:54 ` [PATCH 1/2] btrfs: Add the capability of getting commit stats in BTRFS Ioannis Angelakopoulos
2022-06-11 11:44   ` kernel test robot
2022-06-11 12:55   ` kernel test robot [this message]
2022-06-13 18:59   ` David Sterba
2022-06-13 21:05   ` Sweet Tea Dorminy
2022-06-14 14:15     ` David Sterba
2022-06-10 20:54 ` [PATCH 2/2] btrfs: Expose the BTRFS commit stats through sysfs Ioannis Angelakopoulos
2022-06-13 19:14   ` 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=202206112045.UQwxPCB0-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=iangelak@fb.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kernel-team@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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