From: kernel test robot <lkp@intel.com>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, David Sterba <dsterba@suse.com>
Subject: Re: [PATCH] btrfs: send: remove btrfs_debug() calls
Date: Wed, 30 Apr 2025 17:28:45 +0800 [thread overview]
Message-ID: <202504301726.KJfSXyNW-lkp@intel.com> (raw)
In-Reply-To: <20250429085349.2169622-1-dsterba@suse.com>
Hi David,
kernel test robot noticed the following build warnings:
[auto build test WARNING on kdave/for-next]
[also build test WARNING on linus/master v6.15-rc4 next-20250429]
[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/David-Sterba/btrfs-send-remove-btrfs_debug-calls/20250429-165603
base: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
patch link: https://lore.kernel.org/r/20250429085349.2169622-1-dsterba%40suse.com
patch subject: [PATCH] btrfs: send: remove btrfs_debug() calls
config: arc-randconfig-001-20250430 (https://download.01.org/0day-ci/archive/20250430/202504301726.KJfSXyNW-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250430/202504301726.KJfSXyNW-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/202504301726.KJfSXyNW-lkp@intel.com/
All warnings (new ones prefixed by >>):
fs/btrfs/send.c: In function 'send_rename':
>> fs/btrfs/send.c:819:31: warning: unused variable 'fs_info' [-Wunused-variable]
819 | struct btrfs_fs_info *fs_info = sctx->send_root->fs_info;
| ^~~~~~~
fs/btrfs/send.c: In function 'send_link':
fs/btrfs/send.c:841:31: warning: unused variable 'fs_info' [-Wunused-variable]
841 | struct btrfs_fs_info *fs_info = sctx->send_root->fs_info;
| ^~~~~~~
fs/btrfs/send.c: In function 'send_unlink':
fs/btrfs/send.c:862:31: warning: unused variable 'fs_info' [-Wunused-variable]
862 | struct btrfs_fs_info *fs_info = sctx->send_root->fs_info;
| ^~~~~~~
fs/btrfs/send.c: In function 'send_rmdir':
fs/btrfs/send.c:882:31: warning: unused variable 'fs_info' [-Wunused-variable]
882 | struct btrfs_fs_info *fs_info = sctx->send_root->fs_info;
| ^~~~~~~
fs/btrfs/send.c: In function 'find_extent_clone':
>> fs/btrfs/send.c:1568:13: warning: variable 'logical' set but not used [-Wunused-but-set-variable]
1568 | u64 logical;
| ^~~~~~~
fs/btrfs/send.c: In function 'send_truncate':
fs/btrfs/send.c:2620:31: warning: unused variable 'fs_info' [-Wunused-variable]
2620 | struct btrfs_fs_info *fs_info = sctx->send_root->fs_info;
| ^~~~~~~
fs/btrfs/send.c: In function 'send_chmod':
fs/btrfs/send.c:2645:31: warning: unused variable 'fs_info' [-Wunused-variable]
2645 | struct btrfs_fs_info *fs_info = sctx->send_root->fs_info;
| ^~~~~~~
fs/btrfs/send.c: In function 'send_fileattr':
fs/btrfs/send.c:2670:31: warning: unused variable 'fs_info' [-Wunused-variable]
2670 | struct btrfs_fs_info *fs_info = sctx->send_root->fs_info;
| ^~~~~~~
fs/btrfs/send.c: In function 'send_chown':
fs/btrfs/send.c:2698:31: warning: unused variable 'fs_info' [-Wunused-variable]
2698 | struct btrfs_fs_info *fs_info = sctx->send_root->fs_info;
| ^~~~~~~
fs/btrfs/send.c: In function 'send_utimes':
fs/btrfs/send.c:2724:31: warning: unused variable 'fs_info' [-Wunused-variable]
2724 | struct btrfs_fs_info *fs_info = sctx->send_root->fs_info;
| ^~~~~~~
fs/btrfs/send.c: In function 'send_create_inode':
fs/btrfs/send.c:2839:31: warning: unused variable 'fs_info' [-Wunused-variable]
2839 | struct btrfs_fs_info *fs_info = sctx->send_root->fs_info;
| ^~~~~~~
fs/btrfs/send.c: In function 'send_write':
fs/btrfs/send.c:5308:31: warning: unused variable 'fs_info' [-Wunused-variable]
5308 | struct btrfs_fs_info *fs_info = sctx->send_root->fs_info;
| ^~~~~~~
vim +/fs_info +819 fs/btrfs/send.c
31db9f7c23fbf7e Alexander Block 2012-07-25 812
31db9f7c23fbf7e Alexander Block 2012-07-25 813 /*
31db9f7c23fbf7e Alexander Block 2012-07-25 814 * Sends a move instruction to user space
31db9f7c23fbf7e Alexander Block 2012-07-25 815 */
31db9f7c23fbf7e Alexander Block 2012-07-25 816 static int send_rename(struct send_ctx *sctx,
31db9f7c23fbf7e Alexander Block 2012-07-25 817 struct fs_path *from, struct fs_path *to)
31db9f7c23fbf7e Alexander Block 2012-07-25 818 {
04ab956ee69cdbe Jeff Mahoney 2016-09-20 @819 struct btrfs_fs_info *fs_info = sctx->send_root->fs_info;
31db9f7c23fbf7e Alexander Block 2012-07-25 820 int ret;
31db9f7c23fbf7e Alexander Block 2012-07-25 821
31db9f7c23fbf7e Alexander Block 2012-07-25 822 ret = begin_cmd(sctx, BTRFS_SEND_C_RENAME);
31db9f7c23fbf7e Alexander Block 2012-07-25 823 if (ret < 0)
264515c7cb62661 Filipe Manana 2025-02-20 824 return ret;
31db9f7c23fbf7e Alexander Block 2012-07-25 825
31db9f7c23fbf7e Alexander Block 2012-07-25 826 TLV_PUT_PATH(sctx, BTRFS_SEND_A_PATH, from);
31db9f7c23fbf7e Alexander Block 2012-07-25 827 TLV_PUT_PATH(sctx, BTRFS_SEND_A_PATH_TO, to);
31db9f7c23fbf7e Alexander Block 2012-07-25 828
31db9f7c23fbf7e Alexander Block 2012-07-25 829 ret = send_cmd(sctx);
31db9f7c23fbf7e Alexander Block 2012-07-25 830
31db9f7c23fbf7e Alexander Block 2012-07-25 831 tlv_put_failure:
31db9f7c23fbf7e Alexander Block 2012-07-25 832 return ret;
31db9f7c23fbf7e Alexander Block 2012-07-25 833 }
31db9f7c23fbf7e Alexander Block 2012-07-25 834
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-04-30 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 8:53 [PATCH] btrfs: send: remove btrfs_debug() calls David Sterba
2025-04-30 9:28 ` kernel test robot [this message]
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=202504301726.KJfSXyNW-lkp@intel.com \
--to=lkp@intel.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--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