From: kbuild test robot <lkp@intel.com>
To: Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
kbuild-all@01.org, linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs:dev-test 15/41] include/trace/events/f2fs.h:1287:1: sparse: sparse: cast to restricted vm_fault_t
Date: Wed, 24 Apr 2019 09:26:48 +0800 [thread overview]
Message-ID: <201904240946.5kYJ7xld%lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
head: 2f7ea3581030c1a146db350dc5d3bf068861145b
commit: 93ed4e0804b3b5e9dc7e2cfe522b0a407ab7198c [15/41] f2fs: add tracepoint for f2fs_filemap_fault()
reproduce:
# apt-get install sparse
git checkout 93ed4e0804b3b5e9dc7e2cfe522b0a407ab7198c
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> include/trace/events/f2fs.h:1287:1: sparse: sparse: cast to restricted vm_fault_t
>> include/trace/events/f2fs.h:1287:1: sparse: sparse: cast to restricted vm_fault_t
>> include/trace/events/f2fs.h:1287:1: sparse: sparse: restricted vm_fault_t degrades to integer
>> include/trace/events/f2fs.h:1287:1: sparse: sparse: restricted vm_fault_t degrades to integer
include/asm-generic/atomic-instrumented.h:239:26: sparse: sparse: context imbalance in 'f2fs_drop_inode' - unexpected unlock
vim +1287 include/trace/events/f2fs.h
1286
> 1287 TRACE_EVENT(f2fs_filemap_fault,
1288
1289 TP_PROTO(struct inode *inode, pgoff_t index, enum vm_fault_reason ret),
1290
1291 TP_ARGS(inode, index, ret),
1292
1293 TP_STRUCT__entry(
1294 __field(dev_t, dev)
1295 __field(ino_t, ino)
1296 __field(pgoff_t, index)
1297 __field(enum vm_fault_reason, ret)
1298 ),
1299
1300 TP_fast_assign(
1301 __entry->dev = inode->i_sb->s_dev;
1302 __entry->ino = inode->i_ino;
1303 __entry->index = index;
1304 __entry->ret = ret;
1305 ),
1306
1307 TP_printk("dev = (%d,%d), ino = %lu, index = %lu, ret = %u",
1308 show_dev_ino(__entry),
1309 (unsigned long)__entry->index,
1310 ret)
1311 );
1312
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
reply other threads:[~2019-04-24 1:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201904240946.5kYJ7xld%lkp@intel.com \
--to=lkp@intel.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).