[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4dc9a4eb-403f-951e-16e3-6fae5ed322be@acm.org>
Date: Sun, 17 Jul 2022 07:50:46 -0700
From: Bart Van Assche <bvanassche@....org>
To: kernel test robot <lkp@...el.com>
Cc: kbuild-all@...ts.01.org, Ammar Faizi <ammarfaizi2@...weeb.org>,
GNU/Weeb Mailing List <gwml@...r.gnuweeb.org>,
linux-kernel@...r.kernel.org, Jens Axboe <axboe@...nel.dk>,
Ryusuke Konishi <konishi.ryusuke@...il.com>
Subject: Re: [ammarfaizi2-block:axboe/linux-block/for-next 91/112]
include/trace/events/nilfs2.h:191:1: sparse: sparse: cast to restricted
blk_opf_t
On 7/16/22 08:40, kernel test robot wrote:
> 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
I think the root cause of this and similar reports is in the tracing
core core. I will post a patch.
Thanks,
Bart.
Powered by blists - more mailing lists