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>
Subject: include/trace/events/jbd2.h:356:1: sparse: sparse: cast to restricted blk_opf_t
Date: Mon, 15 Jan 2024 12:28:27 +0800 [thread overview]
Message-ID: <202401151239.cNgBQqgO-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 052d534373b7ed33712a63d5e17b2b6cdbce84fd
commit: 6669797b0dd41ced457760b6e1014fdda8ce19ce fs/jbd2: Fix the documentation of the jbd2_write_superblock() callers
date: 1 year, 6 months ago
config: x86_64-randconfig-121-20240107 (https://download.01.org/0day-ci/archive/20240115/202401151239.cNgBQqgO-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/20240115/202401151239.cNgBQqgO-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/202401151239.cNgBQqgO-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
fs/jbd2/journal.c: note: in included file (through include/trace/trace_events.h, include/trace/define_trace.h, include/trace/events/jbd2.h):
>> include/trace/events/jbd2.h:356:1: sparse: sparse: cast to restricted blk_opf_t
>> include/trace/events/jbd2.h:356:1: sparse: sparse: cast to restricted blk_opf_t
>> include/trace/events/jbd2.h:356:1: sparse: sparse: restricted blk_opf_t degrades to integer
>> include/trace/events/jbd2.h:356:1: sparse: sparse: restricted blk_opf_t degrades to integer
vim +356 include/trace/events/jbd2.h
71f2be213a00090 Theodore Ts'o 2009-12-23 355
24bcc89c7e7c649 Jan Kara 2012-03-13 @356 TRACE_EVENT(jbd2_write_superblock,
2201c590dd6e802 Seiji Aguchi 2012-02-20 357
6669797b0dd41ce Bart Van Assche 2022-07-14 358 TP_PROTO(journal_t *journal, blk_opf_t write_flags),
2201c590dd6e802 Seiji Aguchi 2012-02-20 359
6669797b0dd41ce Bart Van Assche 2022-07-14 360 TP_ARGS(journal, write_flags),
2201c590dd6e802 Seiji Aguchi 2012-02-20 361
2201c590dd6e802 Seiji Aguchi 2012-02-20 362 TP_STRUCT__entry(
2201c590dd6e802 Seiji Aguchi 2012-02-20 363 __field( dev_t, dev )
6669797b0dd41ce Bart Van Assche 2022-07-14 364 __field( blk_opf_t, write_flags )
2201c590dd6e802 Seiji Aguchi 2012-02-20 365 ),
2201c590dd6e802 Seiji Aguchi 2012-02-20 366
2201c590dd6e802 Seiji Aguchi 2012-02-20 367 TP_fast_assign(
2201c590dd6e802 Seiji Aguchi 2012-02-20 368 __entry->dev = journal->j_fs_dev->bd_dev;
6669797b0dd41ce Bart Van Assche 2022-07-14 369 __entry->write_flags = write_flags;
2201c590dd6e802 Seiji Aguchi 2012-02-20 370 ),
2201c590dd6e802 Seiji Aguchi 2012-02-20 371
6669797b0dd41ce Bart Van Assche 2022-07-14 372 TP_printk("dev %d,%d write_flags %x", MAJOR(__entry->dev),
6669797b0dd41ce Bart Van Assche 2022-07-14 373 MINOR(__entry->dev), (__force u32)__entry->write_flags)
2201c590dd6e802 Seiji Aguchi 2012-02-20 374 );
2201c590dd6e802 Seiji Aguchi 2012-02-20 375
:::::: The code at line 356 was first introduced by commit
:::::: 24bcc89c7e7c64982e6192b4952a0a92379fc341 jbd2: split updating of journal superblock and marking journal empty
:::::: TO: Jan Kara <jack@suse.cz>
:::::: CC: Theodore Ts'o <tytso@mit.edu>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-01-15 4:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 4:28 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-09 3:23 kernel test robot
2022-10-06 13:49 kernel test robot
2022-10-06 17: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=202401151239.cNgBQqgO-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--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®