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
Subject: Re: [PATCH 6/7] btrfs: scrub: unify and shorten the error message
Date: Fri, 15 Mar 2024 07:05:07 +0800 [thread overview]
Message-ID: <202403150650.dNFtHzxf-lkp@intel.com> (raw)
In-Reply-To: <6ba44b940e4e3eea573cad667ab8c0b2dd8f2c06.1710409033.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 linus/master v6.8 next-20240314]
[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-scrub-fix-incorrectly-reported-logical-physical-address/20240314-215457
base: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
patch link: https://lore.kernel.org/r/6ba44b940e4e3eea573cad667ab8c0b2dd8f2c06.1710409033.git.wqu%40suse.com
patch subject: [PATCH 6/7] btrfs: scrub: unify and shorten the error message
config: m68k-defconfig (https://download.01.org/0day-ci/archive/20240315/202403150650.dNFtHzxf-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240315/202403150650.dNFtHzxf-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/202403150650.dNFtHzxf-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from fs/btrfs/extent_io.h:16,
from fs/btrfs/locking.h:13,
from fs/btrfs/ctree.h:19,
from fs/btrfs/scrub.c:10:
fs/btrfs/scrub.c: In function 'scrub_print_warning_inode':
>> fs/btrfs/scrub.c:433:35: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
433 | (char *)ipath->fspath->val[i], offset,
| ^
fs/btrfs/messages.h:27:39: note: in definition of macro 'btrfs_printk'
27 | _btrfs_printk(fs_info, fmt, ##args)
| ^~~~
fs/btrfs/messages.h:66:9: note: in expansion of macro 'btrfs_printk_in_rcu'
66 | btrfs_printk_in_rcu(fs_info, KERN_WARNING fmt, ##args)
| ^~~~~~~~~~~~~~~~~~~
fs/btrfs/scrub.c:430:17: note: in expansion of macro 'btrfs_warn_in_rcu'
430 | btrfs_warn_in_rcu(fs_info,
| ^~~~~~~~~~~~~~~~~
vim +433 fs/btrfs/scrub.c
388
389 static int scrub_print_warning_inode(u64 inum, u64 offset, u64 num_bytes,
390 u64 root, void *warn_ctx)
391 {
392 int ret;
393 int i;
394 unsigned nofs_flag;
395 struct scrub_warning *swarn = warn_ctx;
396 struct btrfs_fs_info *fs_info = swarn->dev->fs_info;
397 struct inode_fs_paths *ipath = NULL;
398 struct btrfs_root *local_root;
399
400 local_root = btrfs_get_fs_root(fs_info, root, true);
401 if (IS_ERR(local_root)) {
402 ret = PTR_ERR(local_root);
403 goto err;
404 }
405
406 /*
407 * init_path might indirectly call vmalloc, or use GFP_KERNEL. Scrub
408 * uses GFP_NOFS in this context, so we keep it consistent but it does
409 * not seem to be strictly necessary.
410 */
411 nofs_flag = memalloc_nofs_save();
412 ipath = init_ipath(4096, local_root, swarn->path);
413 memalloc_nofs_restore(nofs_flag);
414 if (IS_ERR(ipath)) {
415 btrfs_put_root(local_root);
416 ret = PTR_ERR(ipath);
417 ipath = NULL;
418 goto err;
419 }
420 ret = paths_from_inode(inum, ipath);
421
422 if (ret < 0)
423 goto err;
424
425 /*
426 * we deliberately ignore the bit ipath might have been too small to
427 * hold all of the paths here
428 */
429 for (i = 0; i < ipath->fspath->elem_cnt; ++i)
430 btrfs_warn_in_rcu(fs_info,
431 "%s at inode %lld/%llu(%s) fileoff %llu, logical %llu(%u) physical %llu(%s)%llu",
432 swarn->errstr, root, inum,
> 433 (char *)ipath->fspath->val[i], offset,
434 swarn->logical, swarn->mirror_num,
435 swarn->dev->devid, btrfs_dev_name(swarn->dev),
436 swarn->physical);
437
438 btrfs_put_root(local_root);
439 free_ipath(ipath);
440 return 0;
441
442 err:
443 btrfs_warn_in_rcu(fs_info,
444 "%s at inode %lld/%llu fileoff %llu, logical %llu(%u) physical %llu(%s)%llu",
445 swarn->errstr, root, inum, offset,
446 swarn->logical, swarn->mirror_num,
447 swarn->dev->devid, btrfs_dev_name(swarn->dev),
448 swarn->physical);
449 free_ipath(ipath);
450 return 0;
451 }
452
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-03-14 23:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 9:50 [PATCH 0/6] btrfs: scrub: refine the error messages Qu Wenruo
2024-03-14 9:50 ` [PATCH 1/7] btrfs: scrub: fix incorrectly reported logical/physical address Qu Wenruo
2024-03-14 12:24 ` Anand Jain
2024-03-14 20:15 ` Qu Wenruo
2024-04-04 20:01 ` David Sterba
2024-03-14 17:10 ` Filipe Manana
2024-03-14 9:50 ` [PATCH 2/7] btrfs: reduce the log level for btrfs_dev_stat_inc_and_print() Qu Wenruo
2024-03-14 17:17 ` Filipe Manana
2024-03-14 20:26 ` Qu Wenruo
2024-03-18 19:54 ` Filipe Manana
2024-03-14 9:50 ` [PATCH 3/7] btrfs: scrub: remove unused is_super parameter from scrub_print_common_warning() Qu Wenruo
2024-03-14 17:19 ` Filipe Manana
2024-03-14 9:50 ` [PATCH 4/7] btrfs: scrub: remove unnecessary dev/physical lookup for scrub_stripe_report_errors() Qu Wenruo
2024-03-14 17:26 ` Filipe Manana
2024-03-14 20:28 ` Qu Wenruo
2024-03-18 16:16 ` Filipe Manana
2024-03-18 19:53 ` Qu Wenruo
2024-03-14 9:50 ` [PATCH 5/7] btrfs: scrub: simplify the inode iteration output Qu Wenruo
2024-03-14 17:29 ` Filipe Manana
2024-03-14 9:50 ` [PATCH 6/7] btrfs: scrub: unify and shorten the error message Qu Wenruo
2024-03-14 17:40 ` Filipe Manana
2024-03-14 20:56 ` Qu Wenruo
2024-03-18 16:26 ` Filipe Manana
2024-03-18 20:00 ` Qu Wenruo
2024-03-14 23:05 ` kernel test robot [this message]
2024-03-15 11:44 ` kernel test robot
2024-03-14 9:50 ` [PATCH 7/7] btrfs: scrub: fix the frequency of error messages Qu Wenruo
2024-03-14 17:51 ` Filipe Manana
2024-03-14 20:32 ` Qu Wenruo
2024-03-14 17:35 ` [PATCH 0/6] btrfs: scrub: refine the " Boris Burkov
2024-03-14 20:30 ` 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=202403150650.dNFtHzxf-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.