Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/4] btrfs: cache max and min order inside btrfs_fs_info
Date: Tue, 2 Sep 2025 11:46:03 +0800	[thread overview]
Message-ID: <202509021022.B3V4xUho-lkp@intel.com> (raw)
In-Reply-To: <d1a3793b551f0a6ccaf8907cc5aa06d8f5b3d5c2.1756703958.git.wqu@suse.com>

Hi Qu,

kernel test robot noticed the following build warnings:

[auto build test WARNING on kdave/for-next]
[also build test WARNING on next-20250901]
[cannot apply to linus/master v6.17-rc4]
[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/Qu-Wenruo/btrfs-support-all-block-sizes-which-is-no-larger-than-page-size/20250901-132648
base:   https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
patch link:    https://lore.kernel.org/r/d1a3793b551f0a6ccaf8907cc5aa06d8f5b3d5c2.1756703958.git.wqu%40suse.com
patch subject: [PATCH 2/4] btrfs: cache max and min order inside btrfs_fs_info
config: x86_64-buildonly-randconfig-004-20250902 (https://download.01.org/0day-ci/archive/20250902/202509021022.B3V4xUho-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14+deb12u1) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250902/202509021022.B3V4xUho-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/202509021022.B3V4xUho-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from fs/btrfs/extent_map.c:10:
   fs/btrfs/btrfs_inode.h: In function 'btrfs_set_inode_mapping_order':
>> fs/btrfs/btrfs_inode.h:530:31: warning: unused variable 'fs_info' [-Wunused-variable]
     530 |         struct btrfs_fs_info *fs_info = inode->root->fs_info;
         |                               ^~~~~~~
--
   In file included from fs/btrfs/tests/../transaction.h:15,
                    from fs/btrfs/tests/delayed-refs-tests.c:4:
   fs/btrfs/tests/../btrfs_inode.h: In function 'btrfs_set_inode_mapping_order':
>> fs/btrfs/tests/../btrfs_inode.h:530:31: warning: unused variable 'fs_info' [-Wunused-variable]
     530 |         struct btrfs_fs_info *fs_info = inode->root->fs_info;
         |                               ^~~~~~~


vim +/fs_info +530 fs/btrfs/btrfs_inode.h

   527	
   528	static inline void btrfs_set_inode_mapping_order(struct btrfs_inode *inode)
   529	{
 > 530		struct btrfs_fs_info *fs_info = inode->root->fs_info;
   531		/* Metadata inode should not reach here. */
   532		ASSERT(is_data_inode(inode));
   533	
   534		/* We only allow BITS_PER_LONGS blocks for each bitmap. */
   535	#ifdef CONFIG_BTRFS_EXPERIMENTAL
   536		mapping_set_folio_order_range(inode->vfs_inode.i_mapping, fs_info->block_min_order,
   537					      fs_info->block_max_order);
   538	#endif
   539	}
   540	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2025-09-02  3:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01  5:24 [PATCH 0/4] btrfs: bs > ps support preparation Qu Wenruo
2025-09-01  5:24 ` [PATCH 1/4] btrfs: support all block sizes which is no larger than page size Qu Wenruo
2025-09-01  5:24 ` [PATCH 2/4] btrfs: cache max and min order inside btrfs_fs_info Qu Wenruo
2025-09-01 18:10   ` David Sterba
2025-09-02  3:46   ` kernel test robot [this message]
2025-09-01  5:24 ` [PATCH 3/4] btrfs: replace single page bio_iter_iovec() usage Qu Wenruo
2025-09-01  6:25   ` Qu Wenruo
2025-09-01  5:24 ` [PATCH 4/4] btrfs: replace bio_for_each_segment usage Qu Wenruo

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=202509021022.B3V4xUho-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=wqu@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