mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Jens Axboe <axboe@kernel.dk>,
	Ryusuke Konishi <konishi.ryusuke@gmail.com>
Subject: include/trace/events/nilfs2.h:191:1: sparse: sparse: cast to restricted blk_opf_t
Date: Tue, 9 Jan 2024 22:16:02 +0800	[thread overview]
Message-ID: <202401092241.I4mm9OWl-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   9f8413c4a66f2fb776d3dc3c9ed20bf435eb305e
commit: ed4512590bd5839f8ea9eef1626b0f4db626b1d1 fs/nilfs2: Use the enum req_op and blk_opf_t types
date:   1 year, 6 months ago
config: x86_64-randconfig-121-20240107 (https://download.01.org/0day-ci/archive/20240109/202401092241.I4mm9OWl-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240109/202401092241.I4mm9OWl-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/202401092241.I4mm9OWl-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   fs/nilfs2/segment.c: note: in included file (through include/trace/trace_events.h, include/trace/define_trace.h, include/trace/events/nilfs2.h):
>> include/trace/events/nilfs2.h:191:1: sparse: sparse: cast to restricted blk_opf_t
>> include/trace/events/nilfs2.h:191:1: sparse: sparse: cast to restricted blk_opf_t
>> include/trace/events/nilfs2.h:191:1: sparse: sparse: restricted blk_opf_t degrades to integer
>> include/trace/events/nilfs2.h:191:1: sparse: sparse: restricted blk_opf_t degrades to integer

vim +191 include/trace/events/nilfs2.h

a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  190  
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06 @191  TRACE_EVENT(nilfs2_mdt_submit_block,
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  192  	    TP_PROTO(struct inode *inode,
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  193  		     unsigned long ino,
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  194  		     unsigned long blkoff,
ed4512590bd5839 Bart Van Assche 2022-07-14  195  		     enum req_op mode),
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  196  
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  197  	    TP_ARGS(inode, ino, blkoff, mode),
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  198  
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  199  	    TP_STRUCT__entry(
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  200  		    __field(struct inode *, inode)
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  201  		    __field(unsigned long, ino)
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  202  		    __field(unsigned long, blkoff)
ed4512590bd5839 Bart Van Assche 2022-07-14  203  		    __field(enum req_op, mode)
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  204  	    ),
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  205  
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  206  	    TP_fast_assign(
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  207  		    __entry->inode = inode;
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  208  		    __entry->ino = ino;
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  209  		    __entry->blkoff = blkoff;
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  210  		    __entry->mode = mode;
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  211  		    ),
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  212  
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  213  	    TP_printk("inode = %p ino = %lu blkoff = %lu mode = %x",
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  214  		      __entry->inode,
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  215  		      __entry->ino,
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  216  		      __entry->blkoff,
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  217  		      __entry->mode)
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  218  );
a9cd207c23ca4fa Hitoshi Mitake  2015-11-06  219  

:::::: The code at line 191 was first introduced by commit
:::::: a9cd207c23ca4fa5bd5f1092e867e87542e349a3 nilfs2: add tracepoints for analyzing reading and writing metadata files

:::::: TO: Hitoshi Mitake <mitake.hitoshi@lab.ntt.co.jp>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2024-01-09 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-09 14:16 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-05  2:03 kernel test robot
2022-08-05  3:07 ` Bart Van Assche

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=202401092241.I4mm9OWl-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=konishi.ryusuke@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®