From: kernel test robot <lkp@intel.com>
To: Naohiro Aota <naohiro.aota@wdc.com>, linux-btrfs@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Naohiro Aota <naohiro.aota@wdc.com>
Subject: Re: [PATCH 5/8] btrfs: zoned: activate metadata block group on write time
Date: Mon, 24 Jul 2023 15:36:53 +0800 [thread overview]
Message-ID: <202307241530.1g5O8gwF-lkp@intel.com> (raw)
In-Reply-To: <2f8e30f966cfd9e06b0745a691bd1a5566aab780.1690171333.git.naohiro.aota@wdc.com>
Hi Naohiro,
kernel test robot noticed the following build errors:
[auto build test ERROR on kdave/for-next]
[also build test ERROR on linus/master v6.5-rc3 next-20230724]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Naohiro-Aota/btrfs-zoned-introduce-block_group-context-for-submit_eb_page/20230724-122053
base: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
patch link: https://lore.kernel.org/r/2f8e30f966cfd9e06b0745a691bd1a5566aab780.1690171333.git.naohiro.aota%40wdc.com
patch subject: [PATCH 5/8] btrfs: zoned: activate metadata block group on write time
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20230724/202307241530.1g5O8gwF-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project.git 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce: (https://download.01.org/0day-ci/archive/20230724/202307241530.1g5O8gwF-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202307241530.1g5O8gwF-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/btrfs/extent_io.c:214:16: warning: variable 'pages_processed' set but not used [-Wunused-but-set-variable]
unsigned long pages_processed = 0;
^
>> fs/btrfs/extent_io.c:1827:60: error: too many arguments to function call, expected 3, have 4
if (!btrfs_check_meta_write_pointer(eb->fs_info, wbc, eb, bg_context)) {
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~~~~~~
fs/btrfs/zoned.h:191:20: note: 'btrfs_check_meta_write_pointer' declared here
static inline bool btrfs_check_meta_write_pointer(struct btrfs_fs_info *fs_info,
^
1 warning and 1 error generated.
vim +1827 fs/btrfs/extent_io.c
1766
1767 /*
1768 * Submit all page(s) of one extent buffer.
1769 *
1770 * @page: the page of one extent buffer
1771 * @eb_context: to determine if we need to submit this page, if current page
1772 * belongs to this eb, we don't need to submit
1773 *
1774 * The caller should pass each page in their bytenr order, and here we use
1775 * @eb_context to determine if we have submitted pages of one extent buffer.
1776 *
1777 * If we have, we just skip until we hit a new page that doesn't belong to
1778 * current @eb_context.
1779 *
1780 * If not, we submit all the page(s) of the extent buffer.
1781 *
1782 * Return >0 if we have submitted the extent buffer successfully.
1783 * Return 0 if we don't need to submit the page, as it's already submitted by
1784 * previous call.
1785 * Return <0 for fatal error.
1786 */
1787 static int submit_eb_page(struct page *page, struct writeback_control *wbc,
1788 struct extent_buffer **eb_context,
1789 struct btrfs_block_group **bg_context)
1790 {
1791 struct address_space *mapping = page->mapping;
1792 struct extent_buffer *eb;
1793 int ret;
1794
1795 if (!PagePrivate(page))
1796 return 0;
1797
1798 if (btrfs_sb(page->mapping->host->i_sb)->nodesize < PAGE_SIZE)
1799 return submit_eb_subpage(page, wbc);
1800
1801 spin_lock(&mapping->private_lock);
1802 if (!PagePrivate(page)) {
1803 spin_unlock(&mapping->private_lock);
1804 return 0;
1805 }
1806
1807 eb = (struct extent_buffer *)page->private;
1808
1809 /*
1810 * Shouldn't happen and normally this would be a BUG_ON but no point
1811 * crashing the machine for something we can survive anyway.
1812 */
1813 if (WARN_ON(!eb)) {
1814 spin_unlock(&mapping->private_lock);
1815 return 0;
1816 }
1817
1818 if (eb == *eb_context) {
1819 spin_unlock(&mapping->private_lock);
1820 return 0;
1821 }
1822 ret = atomic_inc_not_zero(&eb->refs);
1823 spin_unlock(&mapping->private_lock);
1824 if (!ret)
1825 return 0;
1826
> 1827 if (!btrfs_check_meta_write_pointer(eb->fs_info, wbc, eb, bg_context)) {
1828 /*
1829 * If for_sync, this hole will be filled with
1830 * trasnsaction commit.
1831 */
1832 if (wbc->sync_mode == WB_SYNC_ALL && !wbc->for_sync)
1833 ret = -EAGAIN;
1834 else
1835 ret = 0;
1836 free_extent_buffer(eb);
1837 return ret;
1838 }
1839
1840 *eb_context = eb;
1841
1842 if (!lock_extent_buffer_for_io(eb, wbc)) {
1843 free_extent_buffer(eb);
1844 return 0;
1845 }
1846 if (*bg_context) {
1847 /* Implies write in zoned mode. */
1848 struct btrfs_block_group *bg = *bg_context;
1849
1850 /* Mark the last eb in the block group. */
1851 btrfs_schedule_zone_finish_bg(bg, eb);
1852 bg->meta_write_pointer += eb->len;
1853 }
1854 write_one_eb(eb, wbc);
1855 free_extent_buffer(eb);
1856 return 1;
1857 }
1858
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-07-24 7:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 4:18 [PATCH 0/8] btrfs: zoned: write-time activation of metadata block group Naohiro Aota
2023-07-24 4:18 ` [PATCH 1/8] btrfs: zoned: introduce block_group context for submit_eb_page() Naohiro Aota
2023-07-24 15:00 ` Christoph Hellwig
2023-07-25 5:44 ` Naohiro Aota
2023-07-24 4:18 ` [PATCH 2/8] btrfs: zoned: defer advancing meta_write_pointer Naohiro Aota
2023-07-24 15:04 ` Christoph Hellwig
2023-07-25 8:59 ` Naohiro Aota
2023-07-26 13:06 ` hch
2023-07-24 4:18 ` [PATCH 3/8] btrfs: zoned: update meta_write_pointer on zone finish Naohiro Aota
2023-07-24 15:04 ` Christoph Hellwig
2023-07-25 9:01 ` Naohiro Aota
2023-07-24 4:18 ` [PATCH 4/8] btrfs: zoned: reserve zones for an active metadata/system block group Naohiro Aota
2023-07-24 15:06 ` Christoph Hellwig
2023-07-25 9:07 ` Naohiro Aota
2023-07-26 13:07 ` hch
2023-07-24 4:18 ` [PATCH 5/8] btrfs: zoned: activate metadata block group on write time Naohiro Aota
2023-07-24 6:24 ` kernel test robot
2023-07-24 7:36 ` kernel test robot [this message]
2023-07-24 7:57 ` kernel test robot
2023-07-24 15:12 ` Christoph Hellwig
2023-07-25 9:28 ` Naohiro Aota
2023-07-26 13:10 ` hch
2023-07-24 4:18 ` [PATCH 6/8] btrfs: zoned: no longer count fresh BG region as zone unusable Naohiro Aota
2023-07-24 4:18 ` [PATCH 7/8] btrfs: zoned: don't activate non-DATA BG on allocation Naohiro Aota
2023-07-24 4:18 ` [PATCH 8/8] btrfs: zoned: re-enable metadata over-commit for zoned mode Naohiro Aota
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=202307241530.1g5O8gwF-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=naohiro.aota@wdc.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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).