From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>, Eric Biggers <ebiggers@kernel.org>
Subject: fs/crypto/bio.c:67:17: sparse: sparse: cast from restricted blk_status_t
Date: Tue, 23 Jun 2026 01:23:35 +0800 [thread overview]
Message-ID: <202606230102.bgOhUw2D-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: ef0c9f75a19532d7675384708fc8621e10850104
commit: bc26e2efa2c5bb9289fa894834446840dea0bc31 fscrypt: keep multiple bios in flight in fscrypt_zeroout_range_inline_crypt
date: 5 months ago
config: arm-randconfig-r121-20260622 (https://download.01.org/0day-ci/archive/20260623/202606230102.bgOhUw2D-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 12.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260623/202606230102.bgOhUw2D-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
| Fixes: bc26e2efa2c5 ("fscrypt: keep multiple bios in flight in fscrypt_zeroout_range_inline_crypt")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202606230102.bgOhUw2D-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/crypto/bio.c:67:17: sparse: sparse: cast from restricted blk_status_t
fs/crypto/bio.c:67:17: sparse: sparse: cast to restricted blk_status_t
>> fs/crypto/bio.c:67:17: sparse: sparse: cast from restricted blk_status_t
fs/crypto/bio.c:67:17: sparse: sparse: cast to restricted blk_status_t
vim +67 fs/crypto/bio.c
61
62 static void fscrypt_zeroout_range_end_io(struct bio *bio)
63 {
64 struct fscrypt_zero_done *done = bio->bi_private;
65
66 if (bio->bi_status)
> 67 cmpxchg(&done->status, 0, bio->bi_status);
68 fscrypt_zeroout_range_done(done);
69 bio_put(bio);
70 }
71
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-06-22 17:26 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=202606230102.bgOhUw2D-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--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
Powered by JetHome