From: Christophe LEROY <christophe.leroy@c-s.fr>
To: Dan Carpenter <dan.carpenter@oracle.com>,
aneesh.kumar@linux.vnet.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [bug report] powerpc/mm/radix: Add tlbflush routines
Date: Wed, 31 Jan 2018 17:01:04 +0100 [thread overview]
Message-ID: <8ada45aa-9b29-408c-ba6f-c0938dce047b@c-s.fr> (raw)
In-Reply-To: <20180131154521.GA21698@mwanda>
Le 31/01/2018 à 16:45, Dan Carpenter a écrit :
> Hello Aneesh Kumar K.V,
>
> The patch 1a472c9dba6b: "powerpc/mm/radix: Add tlbflush routines"
> from Apr 29, 2016, leads to the following static checker warning:
>
> arch/powerpc/mm/tlb_nohash.c:218 __local_flush_tlb_page()
> warn: always true condition '(pid != ~0) => (0-u32max != u64max)'
>
> arch/powerpc/mm/tlb_nohash.c
> 211 void __local_flush_tlb_page(struct mm_struct *mm, unsigned long vmaddr,
> 212 int tsize, int ind)
> 213 {
> 214 unsigned int pid;
> 215
> 216 preempt_disable();
> 217 pid = mm ? mm->context.id : 0;
> 218 if (pid != MMU_NO_CONTEXT)
> ^^^^^^^^^^^^^^^^^^^^^
> 219 _tlbil_va(vmaddr, pid, tsize, ind);
> 220 preempt_enable();
> 221 }
>
> I don't know very much about PowerPC. The static checker is guessing
> which headers to pull in instead of relying on the build system so there
> are a lot of false positives. It's apparently using the
> arch/powerpc/include/asm/book3s/64/tlbflush.h header which does:
>
> #define MMU_NO_CONTEXT ~0UL
>
> so it's UINT_MAX vs U64_MAX which is making the checker complain.
As far as I can see from arch/powerpc/include/asm/mmu-hash64.h,
mm->context.id is an unsigned long, so pid should also be an unsigned
long, not an unsigned int ?
Christophe
>
> regards,
> dan carpenter
>
next prev parent reply other threads:[~2018-01-31 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 15:45 [bug report] powerpc/mm/radix: Add tlbflush routines Dan Carpenter
2018-01-31 16:01 ` Christophe LEROY [this message]
2018-02-01 3:31 ` Aneesh Kumar K.V
2018-02-01 4:58 ` Michael Ellerman
2018-02-01 9:21 ` Dan Carpenter
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=8ada45aa-9b29-408c-ba6f-c0938dce047b@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=dan.carpenter@oracle.com \
--cc=linuxppc-dev@lists.ozlabs.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