From: kernel test robot <lkp@intel.com>
To: Wu Bo <bo.wu@vivo.com>, linux-kernel@vger.kernel.org
Cc: Chao Yu <yuchao0@huawei.com>,
linux-f2fs-devel@lists.sourceforge.net,
oe-kbuild-all@lists.linux.dev, Wu Bo <wubo.oduw@gmail.com>,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: [f2fs-dev] [PATCH 13/13] f2fs: implement inline tail forward recovery
Date: Wed, 4 Sep 2024 06:47:13 +0800 [thread overview]
Message-ID: <202409040652.Gn2vQXRR-lkp@intel.com> (raw)
In-Reply-To: <b6e9e02244cf2460df1256e257103e2c77fae2a9.1725334811.git.bo.wu@vivo.com>
Hi Wu,
kernel test robot noticed the following build warnings:
[auto build test WARNING on v6.11-rc6]
[also build test WARNING on linus/master]
[cannot apply to jaegeuk-f2fs/dev-test jaegeuk-f2fs/dev next-20240903]
[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/Wu-Bo/f2fs-add-inline-tail-mount-option/20240903-164436
base: v6.11-rc6
patch link: https://lore.kernel.org/r/b6e9e02244cf2460df1256e257103e2c77fae2a9.1725334811.git.bo.wu%40vivo.com
patch subject: [PATCH 13/13] f2fs: implement inline tail forward recovery
config: arc-randconfig-r112-20240903 (https://download.01.org/0day-ci/archive/20240904/202409040652.Gn2vQXRR-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240904/202409040652.Gn2vQXRR-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/202409040652.Gn2vQXRR-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/f2fs/inline.c:428:34: sparse: sparse: restricted __le32 degrades to integer
vim +428 fs/f2fs/inline.c
416
417 int f2fs_recover_inline_tail(struct inode *inode, struct page *npage)
418 {
419 struct f2fs_sb_info *sbi = F2FS_I_SB(inode);
420 struct f2fs_inode *ri = NULL;
421 void *src_addr, *dst_addr;
422 struct page *ipage;
423
424 if (IS_INODE(npage))
425 ri = F2FS_INODE(npage);
426
427 if (f2fs_has_inline_tail(inode) &&
> 428 ri && (ri->i_flags & F2FS_INLINE_TAIL)) {
429 process_inline:
430 if (!(ri->i_inline & F2FS_DATA_EXIST))
431 return 0;
432
433 ipage = f2fs_get_node_page(sbi, inode->i_ino);
434 if (IS_ERR(ipage))
435 return PTR_ERR(ipage);
436
437 f2fs_wait_on_page_writeback(ipage, NODE, true, true);
438
439 src_addr = inline_data_addr(inode, npage);
440 dst_addr = inline_data_addr(inode, ipage);
441 memcpy(dst_addr, src_addr, MAX_INLINE_DATA(inode));
442
443 set_inode_flag(inode, FI_DATA_EXIST);
444
445 set_page_dirty(ipage);
446 f2fs_put_page(ipage, 1);
447 return 0;
448 }
449
450 if (f2fs_has_inline_tail(inode)) {
451 ipage = f2fs_get_node_page(sbi, inode->i_ino);
452 if (IS_ERR(ipage))
453 return PTR_ERR(ipage);
454 f2fs_truncate_inline_inode(inode, ipage, 0);
455 clear_inode_flag(inode, FI_INLINE_TAIL);
456 f2fs_put_page(ipage, 1);
457 } else if (ri && (ri->i_inline & F2FS_INLINE_TAIL)) {
458 int ret;
459
460 ret = f2fs_truncate_blocks(inode,
461 COMPACT_ADDRS_PER_INODE >> PAGE_SHIFT, false);
462 if (ret)
463 return ret;
464 goto process_inline;
465 }
466 return 0;
467 }
468 struct f2fs_dir_entry *f2fs_find_in_inline_dir(struct inode *dir,
469 const struct f2fs_filename *fname,
470 struct page **res_page)
471 {
472 struct f2fs_sb_info *sbi = F2FS_SB(dir->i_sb);
473 struct f2fs_dir_entry *de;
474 struct f2fs_dentry_ptr d;
475 struct page *ipage;
476 void *inline_dentry;
477
478 ipage = f2fs_get_node_page(sbi, dir->i_ino);
479 if (IS_ERR(ipage)) {
480 *res_page = ipage;
481 return NULL;
482 }
483
484 inline_dentry = inline_data_addr(dir, ipage);
485
486 make_dentry_ptr_inline(dir, &d, inline_dentry);
487 de = f2fs_find_target_dentry(&d, fname, NULL);
488 unlock_page(ipage);
489 if (IS_ERR(de)) {
490 *res_page = ERR_CAST(de);
491 de = NULL;
492 }
493 if (de)
494 *res_page = ipage;
495 else
496 f2fs_put_page(ipage, 0);
497
498 return de;
499 }
500
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Wu Bo <bo.wu@vivo.com>, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Jaegeuk Kim <jaegeuk@kernel.org>,
Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
Wu Bo <wubo.oduw@gmail.com>
Subject: Re: [PATCH 13/13] f2fs: implement inline tail forward recovery
Date: Wed, 4 Sep 2024 06:47:13 +0800 [thread overview]
Message-ID: <202409040652.Gn2vQXRR-lkp@intel.com> (raw)
In-Reply-To: <b6e9e02244cf2460df1256e257103e2c77fae2a9.1725334811.git.bo.wu@vivo.com>
Hi Wu,
kernel test robot noticed the following build warnings:
[auto build test WARNING on v6.11-rc6]
[also build test WARNING on linus/master]
[cannot apply to jaegeuk-f2fs/dev-test jaegeuk-f2fs/dev next-20240903]
[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/Wu-Bo/f2fs-add-inline-tail-mount-option/20240903-164436
base: v6.11-rc6
patch link: https://lore.kernel.org/r/b6e9e02244cf2460df1256e257103e2c77fae2a9.1725334811.git.bo.wu%40vivo.com
patch subject: [PATCH 13/13] f2fs: implement inline tail forward recovery
config: arc-randconfig-r112-20240903 (https://download.01.org/0day-ci/archive/20240904/202409040652.Gn2vQXRR-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240904/202409040652.Gn2vQXRR-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/202409040652.Gn2vQXRR-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/f2fs/inline.c:428:34: sparse: sparse: restricted __le32 degrades to integer
vim +428 fs/f2fs/inline.c
416
417 int f2fs_recover_inline_tail(struct inode *inode, struct page *npage)
418 {
419 struct f2fs_sb_info *sbi = F2FS_I_SB(inode);
420 struct f2fs_inode *ri = NULL;
421 void *src_addr, *dst_addr;
422 struct page *ipage;
423
424 if (IS_INODE(npage))
425 ri = F2FS_INODE(npage);
426
427 if (f2fs_has_inline_tail(inode) &&
> 428 ri && (ri->i_flags & F2FS_INLINE_TAIL)) {
429 process_inline:
430 if (!(ri->i_inline & F2FS_DATA_EXIST))
431 return 0;
432
433 ipage = f2fs_get_node_page(sbi, inode->i_ino);
434 if (IS_ERR(ipage))
435 return PTR_ERR(ipage);
436
437 f2fs_wait_on_page_writeback(ipage, NODE, true, true);
438
439 src_addr = inline_data_addr(inode, npage);
440 dst_addr = inline_data_addr(inode, ipage);
441 memcpy(dst_addr, src_addr, MAX_INLINE_DATA(inode));
442
443 set_inode_flag(inode, FI_DATA_EXIST);
444
445 set_page_dirty(ipage);
446 f2fs_put_page(ipage, 1);
447 return 0;
448 }
449
450 if (f2fs_has_inline_tail(inode)) {
451 ipage = f2fs_get_node_page(sbi, inode->i_ino);
452 if (IS_ERR(ipage))
453 return PTR_ERR(ipage);
454 f2fs_truncate_inline_inode(inode, ipage, 0);
455 clear_inode_flag(inode, FI_INLINE_TAIL);
456 f2fs_put_page(ipage, 1);
457 } else if (ri && (ri->i_inline & F2FS_INLINE_TAIL)) {
458 int ret;
459
460 ret = f2fs_truncate_blocks(inode,
461 COMPACT_ADDRS_PER_INODE >> PAGE_SHIFT, false);
462 if (ret)
463 return ret;
464 goto process_inline;
465 }
466 return 0;
467 }
468 struct f2fs_dir_entry *f2fs_find_in_inline_dir(struct inode *dir,
469 const struct f2fs_filename *fname,
470 struct page **res_page)
471 {
472 struct f2fs_sb_info *sbi = F2FS_SB(dir->i_sb);
473 struct f2fs_dir_entry *de;
474 struct f2fs_dentry_ptr d;
475 struct page *ipage;
476 void *inline_dentry;
477
478 ipage = f2fs_get_node_page(sbi, dir->i_ino);
479 if (IS_ERR(ipage)) {
480 *res_page = ipage;
481 return NULL;
482 }
483
484 inline_dentry = inline_data_addr(dir, ipage);
485
486 make_dentry_ptr_inline(dir, &d, inline_dentry);
487 de = f2fs_find_target_dentry(&d, fname, NULL);
488 unlock_page(ipage);
489 if (IS_ERR(de)) {
490 *res_page = ERR_CAST(de);
491 de = NULL;
492 }
493 if (de)
494 *res_page = ipage;
495 else
496 f2fs_put_page(ipage, 0);
497
498 return de;
499 }
500
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-03 22:48 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 8:54 [f2fs-dev] [PATCH 00/13] f2fs: introduce inline tail Wu Bo via Linux-f2fs-devel
2024-09-03 8:54 ` Wu Bo
2024-09-03 8:54 ` [f2fs-dev] [PATCH 01/13] f2fs: add inline tail mount option Wu Bo via Linux-f2fs-devel
2024-09-03 8:54 ` Wu Bo
2024-09-03 8:54 ` [f2fs-dev] [PATCH 02/13] f2fs: add inline tail disk layout definition Wu Bo via Linux-f2fs-devel
2024-09-03 8:54 ` Wu Bo
2024-09-03 8:54 ` [f2fs-dev] [PATCH 03/13] f2fs: implement inline tail write & truncate Wu Bo via Linux-f2fs-devel
2024-09-03 8:54 ` Wu Bo
2024-09-03 8:54 ` [f2fs-dev] [PATCH 04/13] f2fs: implement inline tail read & fiemap Wu Bo via Linux-f2fs-devel
2024-09-03 8:54 ` Wu Bo
2024-09-03 8:54 ` [f2fs-dev] [PATCH 05/13] f2fs: set inline tail flag when create inode Wu Bo via Linux-f2fs-devel
2024-09-03 8:54 ` Wu Bo
2024-09-03 9:49 ` [f2fs-dev] [External Mail] " Huang Jianan via Linux-f2fs-devel
2024-09-03 9:49 ` [External Mail][f2fs-dev] " Huang Jianan
2024-09-03 9:50 ` [f2fs-dev] [External Mail] " Huang Jianan via Linux-f2fs-devel
2024-09-03 9:50 ` [External Mail][f2fs-dev] " Huang Jianan
2024-09-04 3:03 ` [f2fs-dev] " Wu Bo via Linux-f2fs-devel
2024-09-04 3:03 ` Wu Bo
2024-09-03 8:54 ` [f2fs-dev] [PATCH 06/13] f2fs: fix address info has been truncated Wu Bo via Linux-f2fs-devel
2024-09-03 8:54 ` Wu Bo
2024-09-03 8:54 ` [f2fs-dev] [PATCH 07/13] f2fs: support seek for inline tail Wu Bo via Linux-f2fs-devel
2024-09-03 8:54 ` Wu Bo
2024-09-03 8:54 ` [f2fs-dev] [PATCH 08/13] f2fs: convert inline tail when inode expand Wu Bo via Linux-f2fs-devel
2024-09-03 8:54 ` Wu Bo
2024-09-03 8:54 ` [f2fs-dev] [PATCH 09/13] f2fs: fix data loss during inline tail writing Wu Bo via Linux-f2fs-devel
2024-09-03 8:54 ` Wu Bo
2024-09-03 8:54 ` [f2fs-dev] [PATCH 10/13] f2fs: avoid inlining quota files Wu Bo via Linux-f2fs-devel
2024-09-03 8:54 ` Wu Bo
2024-09-03 8:54 ` [f2fs-dev] [PATCH 11/13] f2fs: fix inline tail data lost Wu Bo via Linux-f2fs-devel
2024-09-03 8:54 ` Wu Bo
2024-09-03 8:54 ` [f2fs-dev] [PATCH 12/13] f2fs: convert inline tails to avoid potential issues Wu Bo via Linux-f2fs-devel
2024-09-03 8:54 ` Wu Bo
2024-09-03 8:54 ` [f2fs-dev] [PATCH 13/13] f2fs: implement inline tail forward recovery Wu Bo via Linux-f2fs-devel
2024-09-03 8:54 ` Wu Bo
2024-09-03 22:47 ` kernel test robot [this message]
2024-09-03 22:47 ` kernel test robot
2024-09-03 16:29 ` [f2fs-dev] [PATCH 00/13] f2fs: introduce inline tail Eric Biggers via Linux-f2fs-devel
2024-09-03 16:29 ` Eric Biggers
2024-09-04 3:14 ` Wu Bo via Linux-f2fs-devel
2024-09-04 3:14 ` Wu Bo
2024-09-06 9:02 ` Juhyung Park
2024-09-06 9:02 ` Juhyung Park
2024-09-06 10:57 ` Wu Bo via Linux-f2fs-devel
2024-09-06 10:57 ` Wu Bo
2024-09-06 14:52 ` Juhyung Park
2024-09-06 14:52 ` Juhyung Park
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=202409040652.Gn2vQXRR-lkp@intel.com \
--to=lkp@intel.com \
--cc=bo.wu@vivo.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wubo.oduw@gmail.com \
--cc=yuchao0@huawei.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.