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 06839271471
	for <linux-kernel@vger.kernel.org>; Wed, 25 Feb 2026 14:15:49 +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=1772028952; cv=none; b=hnJNEEI7U597lPmNviDC78ldIIe2e818jwBnlzYVpCkS9HnyBw3XxMwu/KSKZW9e9WcUPtpzUgHPsj285rD2rw6YJIJbwky5XgEvi5/bcKSq6VQ7inaVGfdiC9Zv2UqqWW50hRcAKYwWzDvV0J/GVhvxkefjm6z/ajXewYGNuxI=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1772028952; c=relaxed/simple;
	bh=i5+peS5lr5PWY4PgsN0JxdHHBZUpQTPjz1nx9YE6Mtk=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:Content-Disposition:In-Reply-To; b=kQPvdp6JtRjLGAATXDvRz9GqG26yVG9fsh16zagRU+rW9n4VxGnD1GEIOdaY5s38MZP9JdNTnMK+/PEqMWY7oWKySjKjpIrQvXjXjR8SenPW8slBl6bVjNJxWUvbf3OXPxiCe+JiahHktzfKaUBDw/HL+H1RwYeE2T9buL2IGqI=
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 EAEAA68B05; Wed, 25 Feb 2026 15:15:38 +0100 (CET)
Date: Wed, 25 Feb 2026 15:15:38 +0100
From: Christoph Hellwig <hch@lst.de>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Christoph Hellwig <hch@lst.de>, kernel test robot <lkp@intel.com>,
	linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
	Eric Biggers <ebiggers@kernel.org>, 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
Message-ID: <20260225141538.GA2732@lst.de>
References: <202602230947.uNRsPyBn-lkp@intel.com> <20260224145528.GA13793@lst.de> <aZ3dmvNZnJYxL8vA@arm.com>
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <aZ3dmvNZnJYxL8vA@arm.com>
User-Agent: Mutt/1.5.17 (2007-11-01)

On Tue, Feb 24, 2026 at 05:19:22PM +0000, Catalin Marinas wrote:
> It looks like sparse doesn't like the __bitwise cast to unsigned long in
> the arm64 cmxchg code. We could force the type cast, not sure whether it
> hides any real issues. Another option is to do the force cast in bio.c
> but I don't think that code is doing anything wrong:

I think that's pretty much what the other architectures do.  Note that
we have a few other places doing the same with blk_status_t, this new
code was just copy and pasted and triggered a new warning.