iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: will@kernel.org, iommu@lists.linux-foundation.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] iommu/arm-smmu-v3: Fix endianness annotations
Date: Fri, 18 Sep 2020 17:08:49 +0200	[thread overview]
Message-ID: <20200918150849.GA632295@myrica> (raw)
In-Reply-To: <67ae1b1b-16af-f488-9a07-7c0bf4a03147@arm.com>

On Fri, Sep 18, 2020 at 04:02:26PM +0100, Robin Murphy wrote:
> On 2020-09-18 15:18, Jean-Philippe Brucker wrote:
> > When building with C=1, sparse reports some issues regarding endianness
> > annotations:
> > 
> > arm-smmu-v3.c:221:26: warning: cast to restricted __le64
> > arm-smmu-v3.c:221:24: warning: incorrect type in assignment (different base types)
> > arm-smmu-v3.c:221:24:    expected restricted __le64 [usertype]
> > arm-smmu-v3.c:221:24:    got unsigned long long [usertype]
> > arm-smmu-v3.c:229:20: warning: incorrect type in argument 1 (different base types)
> > arm-smmu-v3.c:229:20:    expected restricted __le64 [usertype] *[assigned] dst
> > arm-smmu-v3.c:229:20:    got unsigned long long [usertype] *ent
> > arm-smmu-v3.c:229:25: warning: incorrect type in argument 2 (different base types)
> > arm-smmu-v3.c:229:25:    expected unsigned long long [usertype] *[assigned] src
> > arm-smmu-v3.c:229:25:    got restricted __le64 [usertype] *
> > arm-smmu-v3.c:396:20: warning: incorrect type in argument 1 (different base types)
> > arm-smmu-v3.c:396:20:    expected restricted __le64 [usertype] *[assigned] dst
> > arm-smmu-v3.c:396:20:    got unsigned long long *
> > arm-smmu-v3.c:396:25: warning: incorrect type in argument 2 (different base types)
> > arm-smmu-v3.c:396:25:    expected unsigned long long [usertype] *[assigned] src
> > arm-smmu-v3.c:396:25:    got restricted __le64 [usertype] *
> > arm-smmu-v3.c:1349:32: warning: invalid assignment: |=
> > arm-smmu-v3.c:1349:32:    left side has type restricted __le64
> > arm-smmu-v3.c:1349:32:    right side has type unsigned long
> > arm-smmu-v3.c:1396:53: warning: incorrect type in argument 3 (different base types)
> > arm-smmu-v3.c:1396:53:    expected restricted __le64 [usertype] *dst
> > arm-smmu-v3.c:1396:53:    got unsigned long long [usertype] *strtab
> > arm-smmu-v3.c:1424:39: warning: incorrect type in argument 1 (different base types)
> > arm-smmu-v3.c:1424:39:    expected unsigned long long [usertype] *[assigned] strtab
> > arm-smmu-v3.c:1424:39:    got restricted __le64 [usertype] *l2ptr
> > 
> > While harmless, they are incorrect and could hide actual errors during
> > development. Fix them.
> 
> Reviewed-by: Robin Murphy <robin.murphy@arm.com>

Thanks!

> > Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> > ---
> > 
> > There is another false positive due to passing INT_MIN to cmpxchg, and
> > __cmpxchg* to truncate them to u8 and u16:
> > 
> > arch/arm64/include/asm/cmpxchg.h:172:1: warning: cast truncates bits from constant value (ffffffff80000000 becomes 0)
> > arch/arm64/include/asm/cmpxchg.h:172:1: warning: cast truncates bits from constant value (ffffffff80000000 becomes 0)
> > 
> > I haven't found a satisfying fix so far, except adding __force to
> > __cmpxchg_case* which could hide actual bugs.
> 
> I guess that's a general issue with the switch(sizeof()) idiom of sparse not
> being aware that those cases are unreachable?

Precisely. I wondered if _Generic could help, but it looks like the
problem is the same.

Thanks,
Jean

_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2020-09-18 15:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 14:18 [PATCH] iommu/arm-smmu-v3: Fix endianness annotations Jean-Philippe Brucker
2020-09-18 15:02 ` Robin Murphy
2020-09-18 15:08   ` Jean-Philippe Brucker [this message]
2020-09-21 18:17 ` Will Deacon

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=20200918150849.GA632295@myrica \
    --to=jean-philippe@linaro.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=robin.murphy@arm.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;
as well as URLs for NNTP newsgroup(s).