From: kernel test robot <lkp@intel.com>
To: Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 6/6] f2fs: add tracepoint for f2fs_vm_page_mkwrite()
Date: Mon, 11 Dec 2023 03:10:40 +0800 [thread overview]
Message-ID: <202312110238.4bSkMypC-lkp@intel.com> (raw)
In-Reply-To: <20231210092040.3374741-6-chao@kernel.org>
Hi Chao,
kernel test robot noticed the following build warnings:
[auto build test WARNING on jaegeuk-f2fs/dev-test]
[also build test WARNING on jaegeuk-f2fs/dev linus/master v6.7-rc4 next-20231208]
[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/Chao-Yu/f2fs-delete-obsolete-FI_DROP_CACHE/20231210-173004
base: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
patch link: https://lore.kernel.org/r/20231210092040.3374741-6-chao%40kernel.org
patch subject: [PATCH 6/6] f2fs: add tracepoint for f2fs_vm_page_mkwrite()
config: x86_64-randconfig-122-20231210 (https://download.01.org/0day-ci/archive/20231211/202312110238.4bSkMypC-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231211/202312110238.4bSkMypC-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/202312110238.4bSkMypC-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
fs/f2fs/super.c: note: in included file (through include/trace/trace_events.h, include/trace/define_trace.h, include/trace/events/f2fs.h):
>> include/trace/events/f2fs.h:1409:1: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned long mask @@ got restricted vm_fault_t @@
include/trace/events/f2fs.h:1409:1: sparse: expected unsigned long mask
include/trace/events/f2fs.h:1409:1: sparse: got restricted vm_fault_t
>> include/trace/events/f2fs.h:1409:1: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned long mask @@ got restricted vm_fault_t @@
include/trace/events/f2fs.h:1409:1: sparse: expected unsigned long mask
include/trace/events/f2fs.h:1409:1: sparse: got restricted vm_fault_t
>> include/trace/events/f2fs.h:1409:1: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned long mask @@ got restricted vm_fault_t @@
include/trace/events/f2fs.h:1409:1: sparse: expected unsigned long mask
include/trace/events/f2fs.h:1409:1: sparse: got restricted vm_fault_t
>> include/trace/events/f2fs.h:1409:1: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned long mask @@ got restricted vm_fault_t @@
include/trace/events/f2fs.h:1409:1: sparse: expected unsigned long mask
include/trace/events/f2fs.h:1409:1: sparse: got restricted vm_fault_t
>> include/trace/events/f2fs.h:1409:1: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned long mask @@ got restricted vm_fault_t @@
include/trace/events/f2fs.h:1409:1: sparse: expected unsigned long mask
include/trace/events/f2fs.h:1409:1: sparse: got restricted vm_fault_t
>> include/trace/events/f2fs.h:1409:1: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned long mask @@ got restricted vm_fault_t @@
include/trace/events/f2fs.h:1409:1: sparse: expected unsigned long mask
include/trace/events/f2fs.h:1409:1: sparse: got restricted vm_fault_t
>> include/trace/events/f2fs.h:1409:1: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned long mask @@ got restricted vm_fault_t @@
include/trace/events/f2fs.h:1409:1: sparse: expected unsigned long mask
include/trace/events/f2fs.h:1409:1: sparse: got restricted vm_fault_t
>> include/trace/events/f2fs.h:1409:1: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned long mask @@ got restricted vm_fault_t @@
include/trace/events/f2fs.h:1409:1: sparse: expected unsigned long mask
include/trace/events/f2fs.h:1409:1: sparse: got restricted vm_fault_t
>> include/trace/events/f2fs.h:1409:1: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned long mask @@ got restricted vm_fault_t @@
include/trace/events/f2fs.h:1409:1: sparse: expected unsigned long mask
include/trace/events/f2fs.h:1409:1: sparse: got restricted vm_fault_t
>> include/trace/events/f2fs.h:1409:1: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned long mask @@ got restricted vm_fault_t @@
include/trace/events/f2fs.h:1409:1: sparse: expected unsigned long mask
include/trace/events/f2fs.h:1409:1: sparse: got restricted vm_fault_t
>> include/trace/events/f2fs.h:1409:1: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned long mask @@ got restricted vm_fault_t @@
include/trace/events/f2fs.h:1409:1: sparse: expected unsigned long mask
include/trace/events/f2fs.h:1409:1: sparse: got restricted vm_fault_t
>> include/trace/events/f2fs.h:1409:1: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned long mask @@ got restricted vm_fault_t @@
include/trace/events/f2fs.h:1409:1: sparse: expected unsigned long mask
include/trace/events/f2fs.h:1409:1: sparse: got restricted vm_fault_t
>> include/trace/events/f2fs.h:1409:1: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned long mask @@ got restricted vm_fault_t @@
include/trace/events/f2fs.h:1409:1: sparse: expected unsigned long mask
include/trace/events/f2fs.h:1409:1: sparse: got restricted vm_fault_t
>> include/trace/events/f2fs.h:1409:1: sparse: sparse: incorrect type in argument 3 (different base types) @@ expected unsigned long flags @@ got restricted vm_fault_t [usertype] ret @@
include/trace/events/f2fs.h:1409:1: sparse: expected unsigned long flags
include/trace/events/f2fs.h:1409:1: sparse: got restricted vm_fault_t [usertype] ret
fs/f2fs/super.c: note: in included file (through include/trace/trace_events.h, include/trace/define_trace.h, include/trace/events/f2fs.h):
include/trace/events/f2fs.h:1121:1: sparse: sparse: cast to restricted blk_opf_t
include/trace/events/f2fs.h:1121:1: sparse: sparse: restricted blk_opf_t degrades to integer
include/trace/events/f2fs.h:1121:1: sparse: sparse: restricted blk_opf_t degrades to integer
include/trace/events/f2fs.h:1121:1: sparse: sparse: cast to restricted blk_opf_t
include/trace/events/f2fs.h:1121:1: sparse: sparse: restricted blk_opf_t degrades to integer
include/trace/events/f2fs.h:1121:1: sparse: sparse: restricted blk_opf_t degrades to integer
include/trace/events/f2fs.h:1180:1: sparse: sparse: cast to restricted blk_opf_t
include/trace/events/f2fs.h:1180:1: sparse: sparse: restricted blk_opf_t degrades to integer
include/trace/events/f2fs.h:1180:1: sparse: sparse: restricted blk_opf_t degrades to integer
include/trace/events/f2fs.h:1180:1: sparse: sparse: cast to restricted blk_opf_t
include/trace/events/f2fs.h:1180:1: sparse: sparse: restricted blk_opf_t degrades to integer
include/trace/events/f2fs.h:1180:1: sparse: sparse: restricted blk_opf_t degrades to integer
>> include/trace/events/f2fs.h:1409:1: sparse: sparse: cast to restricted vm_fault_t
>> include/trace/events/f2fs.h:1409:1: sparse: sparse: restricted vm_fault_t degrades to integer
>> include/trace/events/f2fs.h:1409:1: sparse: sparse: restricted vm_fault_t degrades to integer
fs/f2fs/super.c:1499:35: sparse: sparse: context imbalance in 'f2fs_drop_inode' - unexpected unlock
vim +1409 include/trace/events/f2fs.h
1408
> 1409 DECLARE_EVENT_CLASS(f2fs_mmap,
1410
1411 TP_PROTO(struct inode *inode, pgoff_t index,
1412 vm_flags_t flags, vm_fault_t ret),
1413
1414 TP_ARGS(inode, index, flags, ret),
1415
1416 TP_STRUCT__entry(
1417 __field(dev_t, dev)
1418 __field(ino_t, ino)
1419 __field(pgoff_t, index)
1420 __field(vm_flags_t, flags)
1421 __field(vm_fault_t, ret)
1422 ),
1423
1424 TP_fast_assign(
1425 __entry->dev = inode->i_sb->s_dev;
1426 __entry->ino = inode->i_ino;
1427 __entry->index = index;
1428 __entry->flags = flags;
1429 __entry->ret = ret;
1430 ),
1431
1432 TP_printk("dev = (%d,%d), ino = %lu, index = %lu, flags: %s, ret: %s",
1433 show_dev_ino(__entry),
1434 (unsigned long)__entry->index,
1435 __print_flags(__entry->flags, "|", FAULT_FLAG_TRACE),
1436 __print_flags(__entry->ret, "|", VM_FAULT_RESULT_TRACE))
1437 );
1438
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-12-10 19:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 9:20 [f2fs-dev] [PATCH 1/6] f2fs: delete obsolete FI_FIRST_BLOCK_WRITTEN Chao Yu
2023-12-10 9:20 ` Chao Yu
2023-12-10 9:20 ` [f2fs-dev] [PATCH 2/6] f2fs: delete obsolete FI_DROP_CACHE Chao Yu
2023-12-10 9:20 ` Chao Yu
2023-12-10 9:20 ` [f2fs-dev] [PATCH 3/6] f2fs: introduce get_dnode_addr() to clean up codes Chao Yu
2023-12-10 9:20 ` Chao Yu
2023-12-10 9:20 ` [f2fs-dev] [PATCH 4/6] f2fs: update blkaddr in __set_data_blkaddr() for cleanup Chao Yu
2023-12-10 9:20 ` Chao Yu
2023-12-10 9:20 ` [f2fs-dev] [PATCH 5/6] f2fs: introduce f2fs_invalidate_internal_cache() " Chao Yu
2023-12-10 9:20 ` Chao Yu
2023-12-10 9:20 ` [f2fs-dev] [PATCH 6/6] f2fs: add tracepoint for f2fs_vm_page_mkwrite() Chao Yu
2023-12-10 9:20 ` Chao Yu
2023-12-10 19:10 ` kernel test robot [this message]
2023-12-14 20:50 ` [f2fs-dev] [PATCH 1/6] f2fs: delete obsolete FI_FIRST_BLOCK_WRITTEN patchwork-bot+f2fs
2023-12-14 20:50 ` patchwork-bot+f2fs
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=202312110238.4bSkMypC-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--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.