From: kernel test robot <lkp@intel.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [ebiggers:fscrypt-pending 21/22] fs/crypto/block.c:361:17: sparse: sparse: cast from restricted blk_status_t
Date: Wed, 24 Jun 2026 19:20:21 +0800 [thread overview]
Message-ID: <202606241906.ozL5jpWr-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git fscrypt-pending
head: 458617e964eabfd201862b2ebdc538e7906ddf15
commit: db7c0e5b6866c3230c97157ddf48e548f6ae476b [21/22] fscrypt: Merge bio.c and inline_crypt.c into block.c
config: parisc-randconfig-r121-20260624 (https://download.01.org/0day-ci/archive/20260624/202606241906.ozL5jpWr-lkp@intel.com/config)
compiler: hppa-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/20260624/202606241906.ozL5jpWr-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/202606241906.ozL5jpWr-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/crypto/block.c:361:17: sparse: sparse: cast from restricted blk_status_t
>> fs/crypto/block.c:361:17: sparse: sparse: cast from restricted blk_status_t
>> fs/crypto/block.c:361:17: sparse: sparse: cast to restricted blk_status_t
vim +361 fs/crypto/block.c
355
356 static void fscrypt_zeroout_range_end_io(struct bio *bio)
357 {
358 struct fscrypt_zero_done *done = bio->bi_private;
359
360 if (bio->bi_status)
> 361 cmpxchg(&done->status, 0, bio->bi_status);
362 fscrypt_zeroout_range_done(done);
363 bio_put(bio);
364 }
365
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-06-24 11:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202606241906.ozL5jpWr-lkp@intel.com \
--to=lkp@intel.com \
--cc=ebiggers@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 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.