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
Date: Wed, 25 Feb 2026 15:15:38 +0100 [thread overview]
Message-ID: <20260225141538.GA2732@lst.de> (raw)
In-Reply-To: <aZ3dmvNZnJYxL8vA@arm.com>
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.
prev parent reply other threads:[~2026-02-25 14:15 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 ` fs/crypto/bio.c:67:17: sparse: sparse: cast to restricted blk_status_t Christoph Hellwig
2026-02-24 17:19 ` Catalin Marinas
2026-02-25 14:15 ` Christoph Hellwig [this message]
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=20260225141538.GA2732@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