From: Christoph Hellwig <hch@lst•de>
To: kernel test robot <lkp@intel•com>
Cc: Christoph Hellwig <hch@lst•de>,
oe-kbuild-all@lists•linux.dev, Jens Axboe <axboe@kernel•dk>,
Eric Biggers <ebiggers@kernel•org>,
Madhavan Srinivasan <maddy@linux•ibm.com>,
Michael Ellerman <mpe@ellerman•id.au>,
Nicholas Piggin <npiggin@gmail•com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel•org>,
linuxppc-dev@lists•ozlabs.org
Subject: Re: [axboe:for-7.0/block 19/138] block/blk-crypto-fallback.c:154:17: sparse: sparse: cast from restricted blk_status_t
Date: Mon, 1 Jun 2026 17:29:33 +0200 [thread overview]
Message-ID: <20260601152933.GA6444@lst.de> (raw)
In-Reply-To: <202606012339.rZAl6Xq8-lkp@intel.com>
I think powerpc really need to pick the tricks from other architectures
to make cmpxchg work on __bitwise fields.
On Mon, Jun 01, 2026 at 11:26:16PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git for-7.0/block
> head: 72f4d6fca699a1e35b39c5e5dacac2926d254135
> commit: b37fbce460ad60b0c4449c1c7566cf24f3016713 [19/138] blk-crypto: optimize bio splitting in blk_crypto_fallback_encrypt_bio
> config: powerpc64-randconfig-r111-20260601 (https://download.01.org/0day-ci/archive/20260601/202606012339.rZAl6Xq8-lkp@intel.com/config)
> compiler: powerpc64-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/20260601/202606012339.rZAl6Xq8-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/202606012339.rZAl6Xq8-lkp@intel.com/
>
> sparse warnings: (new ones prefixed by >>)
> >> block/blk-crypto-fallback.c:154:17: sparse: sparse: cast from restricted blk_status_t
> >> block/blk-crypto-fallback.c:154:17: sparse: sparse: cast from restricted blk_status_t
> block/blk-crypto-fallback.c:154:17: sparse: sparse: cast to restricted blk_status_t
>
> vim +154 block/blk-crypto-fallback.c
>
> 143
> 144 static void blk_crypto_fallback_encrypt_endio(struct bio *enc_bio)
> 145 {
> 146 struct bio *src_bio = enc_bio->bi_private;
> 147 int i;
> 148
> 149 for (i = 0; i < enc_bio->bi_vcnt; i++)
> 150 mempool_free(enc_bio->bi_io_vec[i].bv_page,
> 151 blk_crypto_bounce_page_pool);
> 152
> 153 if (enc_bio->bi_status)
> > 154 cmpxchg(&src_bio->bi_status, 0, enc_bio->bi_status);
> 155
> 156 bio_put(enc_bio);
> 157 bio_endio(src_bio);
> 158 }
> 159
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
---end quoted text---
parent reply other threads:[~2026-06-01 15:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <202606012339.rZAl6Xq8-lkp@intel.com>]
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=20260601152933.GA6444@lst.de \
--to=hch@lst$(echo .)de \
--cc=axboe@kernel$(echo .)dk \
--cc=chleroy@kernel$(echo .)org \
--cc=ebiggers@kernel$(echo .)org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=lkp@intel$(echo .)com \
--cc=maddy@linux$(echo .)ibm.com \
--cc=mpe@ellerman$(echo .)id.au \
--cc=npiggin@gmail$(echo .)com \
--cc=oe-kbuild-all@lists$(echo .)linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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