From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 29FCB3806A6 for ; Tue, 24 Feb 2026 14:55:32 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.95.11.211 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771944934; cv=none; b=NLsKubnzb/v5YfdYxyrwfnwHB9aW4OZkv44lTkCXYV4owC8gdpnfJpF9FTEIajGipOh6Mn750iUC3Z1eZWu/2jrf2bgCSIpq+/KL+LtEKmB3dIB4ViN9OHw9E/hNx5TDRCmJh4/XER/2rR1MU4aO4nFNPjZMbFfTLt7Vtcr6Bgo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771944934; c=relaxed/simple; bh=PdCQFvuEXXyneL5dFAGRcxzrxYYtYepJJlNR/ZgwlL8=; h=Date:From:To:Cc:Subject:Message-ID:MIME-Version:Content-Type: Content-Disposition:In-Reply-To; b=VQlgZZEKItJJHmGxeNTgXZDyPd6184u+cGZeCFOSf+fPG79xrKo/4s4sdWaR2YyM2biE0JO8kxfzMYRGMD/Z4SWwehrjssUP7QIWL957LReYZaAi/F4BBfajnXzI2q01uiH88CGLexQHuGdPj+i4kbsIVlh5rgSrL4UW0x1i6ZY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lst.de; spf=pass smtp.mailfrom=lst.de; arc=none smtp.client-ip=213.95.11.211 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lst.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lst.de Received: by verein.lst.de (Postfix, from userid 2407) id 3F4DA68BEB; Tue, 24 Feb 2026 15:55:29 +0100 (CET) Date: Tue, 24 Feb 2026 15:55:28 +0100 From: Christoph Hellwig To: kernel test robot Cc: linux-kernel@vger.kernel.org, Jens Axboe , Eric Biggers , Catalin Marinas , Will Deacon , linux-arm-kernel@lists.infradead.org Subject: Re: fs/crypto/bio.c:67:17: sparse: sparse: cast to restricted blk_status_t Message-ID: <20260224145528.GA13793@lst.de> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202602230947.uNRsPyBn-lkp@intel.com> User-Agent: Mutt/1.5.17 (2007-11-01) 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 > | 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---