From: kernel test robot <lkp@intel.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: oe-kbuild-all@lists.linux.dev, David Sterba <dsterba@suse.com>,
Daniel Vacek <neelx@suse.com>
Subject: [kdave-btrfs-devel:ext/dv/fscrypt 32/43] fs/btrfs/fscrypt.c:240:34: sparse: sparse: incorrect type in return expression (different base types)
Date: Thu, 14 May 2026 09:50:45 +0800 [thread overview]
Message-ID: <202605140957.DjseWRNF-lkp@intel.com> (raw)
tree: https://github.com/kdave/btrfs-devel.git ext/dv/fscrypt
head: 4c05f02641d57f578a685f7e8d27b9cb18d17cc7
commit: fda37caa264ff597b0fc03039dc95e392432bbc5 [32/43] btrfs: implement process_bio cb for fscrypt
config: alpha-randconfig-r122-20260514 (https://download.01.org/0day-ci/archive/20260514/202605140957.DjseWRNF-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 8.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260514/202605140957.DjseWRNF-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/202605140957.DjseWRNF-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/btrfs/fscrypt.c:240:34: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted blk_status_t @@ got int @@
fs/btrfs/fscrypt.c:240:34: sparse: expected restricted blk_status_t
fs/btrfs/fscrypt.c:240:34: sparse: got int
vim +240 fs/btrfs/fscrypt.c
215
216 static blk_status_t btrfs_process_encrypted_bio(struct bio *orig_bio,
217 struct bio *enc_bio)
218 {
219 struct btrfs_bio *bbio;
220
221 /*
222 * If our bio is from the normal fs_bio_set then we know this is a
223 * mirror split and we can skip it, we'll get the real bio on the last
224 * mirror and we can process that one.
225 */
226 if (orig_bio->bi_pool == &fs_bio_set)
227 return BLK_STS_OK;
228
229 bbio = btrfs_bio(orig_bio);
230
231 if (bio_op(orig_bio) == REQ_OP_READ) {
232 /*
233 * We have ->saved_iter based on the orig_bio, so if the block
234 * layer changes we need to notice this asap so we can update
235 * our code to handle the new world order.
236 */
237 ASSERT(orig_bio == enc_bio);
238 return btrfs_check_encrypted_read_bio(bbio, enc_bio);
239 }
> 240 return btrfs_csum_one_bio(bbio, enc_bio, false);
241 }
242
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-05-14 1:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 1:50 kernel test robot [this message]
2026-05-14 15:53 ` [kdave-btrfs-devel:ext/dv/fscrypt 32/43] fs/btrfs/fscrypt.c:240:34: sparse: sparse: incorrect type in return expression (different base types) Daniel Vacek
2026-05-15 15:04 ` David Sterba
2026-05-18 7:16 ` Daniel Vacek
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=202605140957.DjseWRNF-lkp@intel.com \
--to=lkp@intel.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=neelx@suse.com \
--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.