From: Christoph Hellwig <hch@lst.de>
To: kernel test robot <lkp@intel.com>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Eric Biggers <ebiggers@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: fs/crypto/bio.c:67:17: sparse: sparse: cast to restricted blk_status_t
Date: Tue, 24 Feb 2026 15:55:28 +0100 [thread overview]
Message-ID: <20260224145528.GA13793@lst.de> (raw)
In-Reply-To: <202602230947.uNRsPyBn-lkp@intel.com>
It looks like some arm64 configs generate sparse warnings when using
cmpxchg on __bitwise types. Any chance I could prod the arm64 maintainers
into looking into this?
On Mon, Feb 23, 2026 at 09:23:07AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f
> commit: bc26e2efa2c5bb9289fa894834446840dea0bc31 fscrypt: keep multiple bios in flight in fscrypt_zeroout_range_inline_crypt
> date: 6 weeks ago
> config: arm64-randconfig-r134-20260223 (https://download.01.org/0day-ci/archive/20260223/202602230947.uNRsPyBn-lkp@intel.com/config)
> compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project d8f778935a5bf8a173a3c1d886fd736a4ef6cf05)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260223/202602230947.uNRsPyBn-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/202602230947.uNRsPyBn-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
>
> 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
---end quoted text---
next parent reply other threads:[~2026-02-24 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202602230947.uNRsPyBn-lkp@intel.com>
2026-02-24 14:55 ` Christoph Hellwig [this message]
2026-02-24 17:19 ` fs/crypto/bio.c:67:17: sparse: sparse: cast to restricted blk_status_t Catalin Marinas
2026-02-25 14:15 ` Christoph Hellwig
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=20260224145528.GA13793@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=catalin.marinas@arm.com \
--cc=ebiggers@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=will@kernel.org \
/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