All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [koverstreet-bcachefs:bcachefs-testing 19/101] fs/bcachefs/util/util.c:807:9: sparse: sparse: restricted blk_opf_t degrades to integer
Date: Wed, 16 Sep 2026 18:25:12 +0800	[thread overview]
Message-ID: <202609161837.pgkwJSHR-lkp@intel.com> (raw)

tree:   https://github.com/koverstreet/bcachefs bcachefs-testing
head:   ca944a61e079450f82be88c91e349638c75cf4b6
commit: 6caf75dbc37a5d4876a4b96f48e86a24c66c84fe [19/101] bcachefs: Improve bch2_bio_to_text()
config: openrisc-randconfig-r112-20260915 (https://download.01.org/0day-ci/archive/20260916/202609161837.pgkwJSHR-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 15.2.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260916/202609161837.pgkwJSHR-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/202609161837.pgkwJSHR-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> fs/bcachefs/util/util.c:807:9: sparse: sparse: restricted blk_opf_t degrades to integer
   fs/bcachefs/util/util.c:808:9: sparse: sparse: restricted blk_opf_t degrades to integer

vim +807 fs/bcachefs/util/util.c

   794	
   795	void bch2_bio_to_text(struct printbuf *out, struct bio *bio)
   796	{
   797		if (!out->nr_tabstops)
   798			printbuf_tabstop_push(out, 24);
   799	
   800		prt_printf(out, "bi_bdev:\t");
   801		if (bio->bi_bdev)
   802			prt_bdevname(out, bio->bi_bdev);
   803		else
   804			prt_str(out, "(null|");
   805		prt_newline(out);
   806	
 > 807		prt_printf(out, "bi_opf:\t%s ", bch2_request_op_strs[bio_op(bio)]);
   808		prt_bitflags(out, bch2_request_flag_strs, bio->bi_opf >> REQ_OP_BITS);
   809		prt_newline(out);
   810	
   811		prt_str(out, "bi_flags:\t");
   812		prt_bitflags(out, bch2_bio_flag_strs, bio->bi_flags);
   813		prt_newline(out);
   814	
   815		prt_printf(out, "bi_status:\t%u\n", bio->bi_status);
   816	
   817		prt_printf(out, "bi_iter.bi_sector\t%llu\n",	(u64) bio->bi_iter.bi_sector);
   818		prt_printf(out, "bi_iter.bi_size\t%u\n",	bio->bi_iter.bi_size);
   819		prt_printf(out, "bi_iter.bi_idx\t%u\n",		bio->bi_iter.bi_idx);
   820		prt_printf(out, "bi_iter.bi_bvec_done\t%u\n",	bio->bi_iter.bi_bvec_done);
   821	
   822		prt_printf(out, "bi_remaining:\t%u\n",		atomic_read(&bio->__bi_remaining));
   823		prt_printf(out, "bi_end_io:\t%ps\n",		bio->bi_end_io);
   824	
   825		prt_printf(out, "bi_vcnt\t%u\n",		bio->bi_vcnt);
   826		prt_printf(out, "bi_max_vecs\t%u\n",		bio->bi_max_vecs);
   827	}
   828	

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

             reply	other threads:[~2026-09-16 10:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 10:25 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-16  2:08 [koverstreet-bcachefs:bcachefs-testing 19/101] fs/bcachefs/util/util.c:807:9: sparse: sparse: restricted blk_opf_t degrades to integer kernel test robot

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=202609161837.pgkwJSHR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kent.overstreet@linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.