From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib/iomem_copy: fix __iomem casts
Date: Mon, 29 Jun 2026 12:14:05 +0100 [thread overview]
Message-ID: <1bf23afc-0403-4152-ae8c-fd695bdf5b7e@codethink.co.uk> (raw)
In-Reply-To: <20260624162507.GJ2636677@ZenIV>
On 24/06/2026 17:25, Al Viro wrote:
> On Wed, Jun 24, 2026 at 11:17:17AM +0100, Ben Dooks wrote:
>> On 24/06/2026 00:47, Al Viro wrote:
>>> On Mon, Jun 22, 2026 at 01:48:57PM +0100, Ben Dooks wrote:
>>>> The iomem_copy.c code discards __iomem address space when using
>>>> the IS_ALIGNED() macro. It would make more sense to fix this in
>>>> one place by aing a PTR_ALIGNED_LONG() macro and then doing the
>>>> necessary casts there before invoking IS_ALIGNED().
>>>>
>>>> As part of this, also force the pointer to an unsigned long as
>>>> pointers are generally not signed, although there is no warning
>>>> as yet on treating pointers as signed.
>>>
>>>> +#define PTR_ALIGNED_LONG(__ptr) IS_ALIGNED((__force unsigned long)__ptr, sizeof(long))
>>>
>>> Casting to unsigned long is fine (indeed, casting a pointer to long had
>>> been very odd in the first place), but... why __force? Casts to unsigned long
>>> (de facto uintptr_t) do *not* require __force - they are explicitly allowed,
>>> unless you pass -Wcast-from-as in sparse arguments. -Wall does not turn
>>> those on; -Wsparse-all would, but kbuild doesn't pass that.
>>
>> Trying to get rid of the address space warning, which requires the
>> __force part.
>
> It does not require __force - not with the type we are casting to being
> unsigned long. As the examples you've quoted demonstrate. See
> evaluate_cast() in sparse evaluate.c:
> if ((ttype == &ulong_ctype || ttype == uintptr_ctype) && !Wcast_from_as)
> tas = &bad_address_space;
> with
> if (!tas && valid_as(sas))
> warning(expr->pos, "cast removes address space '%s' of expression", show_as(sas));
> several lines below.
>
> And yes, it is deliberate.
Ah we should also have checked for intptr or long type there,
the original code had long which causes sparse to complain here.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
https://www.codethink.co.uk/privacy.html
prev parent reply other threads:[~2026-06-29 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 12:48 Ben Dooks
2026-06-23 23:47 ` Al Viro
2026-06-24 0:04 ` Al Viro
2026-06-24 8:21 ` David Laight
2026-06-24 10:17 ` Ben Dooks
2026-06-24 16:25 ` Al Viro
2026-06-29 11:14 ` Ben Dooks [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=1bf23afc-0403-4152-ae8c-fd695bdf5b7e@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®