From: Nathan Chancellor <natechancellor@gmail.com>
To: Nathan Huckleberry <nhuck@google.com>
Cc: catalin.marinas@arm.com, will@kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
clang-built-linux@googlegroups.com
Subject: Re: [PATCH] arm64: mm: Fix dead assignment of old_pte
Date: Tue, 2 Jul 2019 16:24:59 -0700 [thread overview]
Message-ID: <20190702232459.GA14941@archlinux-epyc> (raw)
In-Reply-To: <20190702231302.60727-1-nhuck@google.com>
On Tue, Jul 02, 2019 at 04:13:02PM -0700, 'Nathan Huckleberry' via Clang Built Linux wrote:
> When analyzed with the clang static analyzer the
> following warning occurs
>
> line 251, column 2
> Value stored to 'old_pte' is never read
>
> This warning is repeated every time pgtable.h is
> included by another file and produces ~3500
> extra warnings.
>
> Moving old_pte into preprocessor guard.
>
> Cc: clang-built-linux@googlegroups.com
> Signed-off-by: Nathan Huckleberry <nhuck@google.com>
> ---
> arch/arm64/include/asm/pgtable.h | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/include/asm/pgtable.h b/arch/arm64/include/asm/pgtable.h
> index fca26759081a..42ca4fc67f27 100644
> --- a/arch/arm64/include/asm/pgtable.h
> +++ b/arch/arm64/include/asm/pgtable.h
> @@ -238,8 +238,6 @@ extern void __sync_icache_dcache(pte_t pteval);
> static inline void set_pte_at(struct mm_struct *mm, unsigned long addr,
> pte_t *ptep, pte_t pte)
> {
> - pte_t old_pte;
> -
> if (pte_present(pte) && pte_user_exec(pte) && !pte_special(pte))
> __sync_icache_dcache(pte);
>
> @@ -248,8 +246,11 @@ static inline void set_pte_at(struct mm_struct *mm, unsigned long addr,
> * hardware updates of the pte (ptep_set_access_flags safely changes
> * valid ptes without going through an invalid entry).
> */
> + #if IS_ENABLED(CONFIG_DEBUG_VM)
> + pte_t old_pte;
> +
> old_pte = READ_ONCE(*ptep);
> - if (IS_ENABLED(CONFIG_DEBUG_VM) && pte_valid(old_pte) && pte_valid(pte) &&
> + if (pte_valid(old_pte) && pte_valid(pte) &&
> (mm == current->active_mm || atomic_read(&mm->mm_users) > 1)) {
> VM_WARN_ONCE(!pte_young(pte),
> "%s: racy access flag clearing: 0x%016llx -> 0x%016llx",
> @@ -258,6 +259,7 @@ static inline void set_pte_at(struct mm_struct *mm, unsigned long addr,
> "%s: racy dirty state clearing: 0x%016llx -> 0x%016llx",
> __func__, pte_val(old_pte), pte_val(pte));
> }
> + #endif
>
> set_pte(ptep, pte);
> }
> --
> 2.22.0.410.gd8fdbe21b5-goog
>
Hi Nathan,
This does not apply on -next because of https://git.kernel.org/arm64/c/9b604722059039a1a3ff69fb8dfd024264046024.
I would get into the habit of testing -next to see if the warning is
present there first because someone may have independently fixed it
already (I'd be surprised if it wasn't fixed by that commit from a quick
glance).
Additionally, when I do apply this patch to mainline and build, I see
the following warning:
In file included from /home/nathan/cbl/linux/arch/arm64/kernel/asm-offsets.c:10:
In file included from /home/nathan/cbl/linux/include/linux/arm_sdei.h:14:
In file included from /home/nathan/cbl/linux/include/acpi/ghes.h:5:
In file included from /home/nathan/cbl/linux/include/acpi/apei.h:9:
In file included from /home/nathan/cbl/linux/include/linux/acpi.h:34:
In file included from /home/nathan/cbl/linux/include/acpi/acpi_io.h:5:
In file included from /home/nathan/cbl/linux/include/linux/io.h:13:
In file included from /home/nathan/cbl/linux/arch/arm64/include/asm/io.h:18:
/home/nathan/cbl/linux/arch/arm64/include/asm/pgtable.h:250:8: warning: ISO C90 forbids mixing declarations and code [-Wdeclaration-after-statement]
pte_t old_pte;
^
1 warning generated.
Cheers,
Nathan
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Nathan Chancellor <natechancellor@gmail.com>
To: Nathan Huckleberry <nhuck@google.com>
Cc: catalin.marinas@arm.com, will@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com
Subject: Re: [PATCH] arm64: mm: Fix dead assignment of old_pte
Date: Tue, 2 Jul 2019 16:24:59 -0700 [thread overview]
Message-ID: <20190702232459.GA14941@archlinux-epyc> (raw)
In-Reply-To: <20190702231302.60727-1-nhuck@google.com>
On Tue, Jul 02, 2019 at 04:13:02PM -0700, 'Nathan Huckleberry' via Clang Built Linux wrote:
> When analyzed with the clang static analyzer the
> following warning occurs
>
> line 251, column 2
> Value stored to 'old_pte' is never read
>
> This warning is repeated every time pgtable.h is
> included by another file and produces ~3500
> extra warnings.
>
> Moving old_pte into preprocessor guard.
>
> Cc: clang-built-linux@googlegroups.com
> Signed-off-by: Nathan Huckleberry <nhuck@google.com>
> ---
> arch/arm64/include/asm/pgtable.h | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/include/asm/pgtable.h b/arch/arm64/include/asm/pgtable.h
> index fca26759081a..42ca4fc67f27 100644
> --- a/arch/arm64/include/asm/pgtable.h
> +++ b/arch/arm64/include/asm/pgtable.h
> @@ -238,8 +238,6 @@ extern void __sync_icache_dcache(pte_t pteval);
> static inline void set_pte_at(struct mm_struct *mm, unsigned long addr,
> pte_t *ptep, pte_t pte)
> {
> - pte_t old_pte;
> -
> if (pte_present(pte) && pte_user_exec(pte) && !pte_special(pte))
> __sync_icache_dcache(pte);
>
> @@ -248,8 +246,11 @@ static inline void set_pte_at(struct mm_struct *mm, unsigned long addr,
> * hardware updates of the pte (ptep_set_access_flags safely changes
> * valid ptes without going through an invalid entry).
> */
> + #if IS_ENABLED(CONFIG_DEBUG_VM)
> + pte_t old_pte;
> +
> old_pte = READ_ONCE(*ptep);
> - if (IS_ENABLED(CONFIG_DEBUG_VM) && pte_valid(old_pte) && pte_valid(pte) &&
> + if (pte_valid(old_pte) && pte_valid(pte) &&
> (mm == current->active_mm || atomic_read(&mm->mm_users) > 1)) {
> VM_WARN_ONCE(!pte_young(pte),
> "%s: racy access flag clearing: 0x%016llx -> 0x%016llx",
> @@ -258,6 +259,7 @@ static inline void set_pte_at(struct mm_struct *mm, unsigned long addr,
> "%s: racy dirty state clearing: 0x%016llx -> 0x%016llx",
> __func__, pte_val(old_pte), pte_val(pte));
> }
> + #endif
>
> set_pte(ptep, pte);
> }
> --
> 2.22.0.410.gd8fdbe21b5-goog
>
Hi Nathan,
This does not apply on -next because of https://git.kernel.org/arm64/c/9b604722059039a1a3ff69fb8dfd024264046024.
I would get into the habit of testing -next to see if the warning is
present there first because someone may have independently fixed it
already (I'd be surprised if it wasn't fixed by that commit from a quick
glance).
Additionally, when I do apply this patch to mainline and build, I see
the following warning:
In file included from /home/nathan/cbl/linux/arch/arm64/kernel/asm-offsets.c:10:
In file included from /home/nathan/cbl/linux/include/linux/arm_sdei.h:14:
In file included from /home/nathan/cbl/linux/include/acpi/ghes.h:5:
In file included from /home/nathan/cbl/linux/include/acpi/apei.h:9:
In file included from /home/nathan/cbl/linux/include/linux/acpi.h:34:
In file included from /home/nathan/cbl/linux/include/acpi/acpi_io.h:5:
In file included from /home/nathan/cbl/linux/include/linux/io.h:13:
In file included from /home/nathan/cbl/linux/arch/arm64/include/asm/io.h:18:
/home/nathan/cbl/linux/arch/arm64/include/asm/pgtable.h:250:8: warning: ISO C90 forbids mixing declarations and code [-Wdeclaration-after-statement]
pte_t old_pte;
^
1 warning generated.
Cheers,
Nathan
next prev parent reply other threads:[~2019-07-02 23:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 23:13 [PATCH] arm64: mm: Fix dead assignment of old_pte Nathan Huckleberry
2019-07-02 23:13 ` Nathan Huckleberry
2019-07-02 23:24 ` Nathan Chancellor [this message]
2019-07-02 23:24 ` Nathan Chancellor
2019-07-02 23:26 ` Nathan Huckleberry
2019-07-02 23:26 ` Nathan Huckleberry
2019-07-02 23:41 ` [PATCH v2] " Nathan Huckleberry
2019-07-02 23:41 ` Nathan Huckleberry
2019-07-03 8:31 ` Vladimir Murzin
2019-07-03 8:31 ` Vladimir Murzin
2019-07-03 9:17 ` Will Deacon
2019-07-03 9:17 ` Will Deacon
2019-07-03 11:23 ` Mark Rutland
2019-07-03 11:23 ` Mark Rutland
2019-07-03 17:24 ` Nathan Huckleberry
2019-07-03 17:24 ` Nathan Huckleberry
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=20190702232459.GA14941@archlinux-epyc \
--to=natechancellor@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhuck@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.