public inbox for [email protected]
 help / color / mirror / Atom feed
From: kernel test robot <[email protected]>
To: Bart Van Assche <[email protected]>
Cc: [email protected], Ammar Faizi <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>,
	[email protected], Jens Axboe <[email protected]>,
	Ryusuke Konishi <[email protected]>
Subject: [ammarfaizi2-block:axboe/linux-block/for-next 91/112] include/trace/events/nilfs2.h:191:1: sparse: sparse: cast to restricted blk_opf_t
Date: Sat, 16 Jul 2022 23:40:10 +0800	[thread overview]
Message-ID: <[email protected]> (raw)

tree:   https://github.com/ammarfaizi2/linux-block axboe/linux-block/for-next
head:   b1fc9e8ad3d2d294d15e87d57af00890cd23cfc4
commit: ed4512590bd5839f8ea9eef1626b0f4db626b1d1 [91/112] fs/nilfs2: Use the enum req_op and blk_opf_t types
config: mips-randconfig-s033-20220715 (https://download.01.org/0day-ci/archive/20220716/[email protected]/config)
compiler: mips-linux-gcc (GCC) 12.1.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # apt-get install sparse
        # sparse version: v0.6.4-39-gce1a6720-dirty
        # https://github.com/ammarfaizi2/linux-block/commit/ed4512590bd5839f8ea9eef1626b0f4db626b1d1
        git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
        git fetch --no-tags ammarfaizi2-block axboe/linux-block/for-next
        git checkout ed4512590bd5839f8ea9eef1626b0f4db626b1d1
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=mips SHELL=/bin/bash fs/nilfs2/ fs/zonefs/./

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <[email protected]>


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

a9cd207c23ca4f Hitoshi Mitake  2015-11-06  190  
a9cd207c23ca4f Hitoshi Mitake  2015-11-06 @191  TRACE_EVENT(nilfs2_mdt_submit_block,
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  192  	    TP_PROTO(struct inode *inode,
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  193  		     unsigned long ino,
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  194  		     unsigned long blkoff,
ed4512590bd583 Bart Van Assche 2022-07-14  195  		     enum req_op mode),
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  196  
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  197  	    TP_ARGS(inode, ino, blkoff, mode),
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  198  
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  199  	    TP_STRUCT__entry(
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  200  		    __field(struct inode *, inode)
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  201  		    __field(unsigned long, ino)
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  202  		    __field(unsigned long, blkoff)
ed4512590bd583 Bart Van Assche 2022-07-14  203  		    __field(enum req_op, mode)
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  204  	    ),
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  205  
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  206  	    TP_fast_assign(
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  207  		    __entry->inode = inode;
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  208  		    __entry->ino = ino;
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  209  		    __entry->blkoff = blkoff;
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  210  		    __entry->mode = mode;
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  211  		    ),
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  212  
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  213  	    TP_printk("inode = %p ino = %lu blkoff = %lu mode = %x",
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  214  		      __entry->inode,
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  215  		      __entry->ino,
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  216  		      __entry->blkoff,
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  217  		      __entry->mode)
a9cd207c23ca4f Hitoshi Mitake  2015-11-06  218  );
a9cd207c23ca4f 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 <[email protected]>
:::::: CC: Linus Torvalds <[email protected]>

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

             reply	other threads:[~2022-07-16 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-16 15:40 kernel test robot [this message]
2022-07-17 14:50 ` [ammarfaizi2-block:axboe/linux-block/for-next 91/112] include/trace/events/nilfs2.h:191:1: sparse: sparse: cast to restricted blk_opf_t 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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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