From: Uros Bizjak <ubizjak@gmail.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] mm/kmemleak: Use explicit cast to cast pointer from percpu to generic AS
Date: Sun, 18 Aug 2024 21:51:43 +0200 [thread overview]
Message-ID: <CAFULd4aFsoLxs57W6EfddcvZiy=oQ7SMVhSCkvNcPXDvXy6h+Q@mail.gmail.com> (raw)
In-Reply-To: <20240818152634.17443-1-ubizjak@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2324 bytes --]
On Sun, Aug 18, 2024 at 5:26 PM Uros Bizjak <ubizjak@gmail.com> wrote:
>
> Use explicit cast to cast pointer from percpu to generic address space.
>
> The patch will avoid future build errors due to pointer address
> space mismatch with enabled strict percpu address space checks.
>
> The patch also fixes following sparse warnings:
>
> kmemleak.c:1063:39: warning: cast removes address space '__percpu' of expression
> kmemleak.c:1138:37: warning: cast removes address space '__percpu' of expression
>
> Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
Actually, we can do something around the lines of the attached patch
and still keep the __must_check directive active.
Please disregard this patch, a new (better) approach is in the works.
Uros.
> ---
> v2: Use explicit casts instead of IS_ERR_PCPU().
> ---
> mm/kmemleak.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/mm/kmemleak.c b/mm/kmemleak.c
> index 764b08100570..fc2e09ec48f8 100644
> --- a/mm/kmemleak.c
> +++ b/mm/kmemleak.c
> @@ -1059,8 +1059,9 @@ void __ref kmemleak_alloc_percpu(const void __percpu *ptr, size_t size,
> * Percpu allocations are only scanned and not reported as leaks
> * (min_count is set to 0).
> */
> - if (kmemleak_enabled && ptr && !IS_ERR(ptr))
> - create_object_percpu((unsigned long)ptr, size, 0, gfp);
> + if (kmemleak_enabled && ptr &&
> + !IS_ERR((const void *)(__force const unsigned long)ptr))
> + create_object_percpu((__force unsigned long)ptr, size, 0, gfp);
> }
> EXPORT_SYMBOL_GPL(kmemleak_alloc_percpu);
>
> @@ -1134,8 +1135,9 @@ void __ref kmemleak_free_percpu(const void __percpu *ptr)
> {
> pr_debug("%s(0x%px)\n", __func__, ptr);
>
> - if (kmemleak_free_enabled && ptr && !IS_ERR(ptr))
> - delete_object_full((unsigned long)ptr, OBJECT_PERCPU);
> + if (kmemleak_free_enabled && ptr &&
> + !IS_ERR((const void *)(__force const unsigned long)ptr))
> + delete_object_full((__force unsigned long)ptr, OBJECT_PERCPU);
> }
> EXPORT_SYMBOL_GPL(kmemleak_free_percpu);
>
> --
> 2.42.0
>
[-- Attachment #2: p.diff.txt --]
[-- Type: text/plain, Size: 996 bytes --]
diff --git a/include/linux/err.h b/include/linux/err.h
index b5d9bb2a2349..6dd7f00d422d 100644
--- a/include/linux/err.h
+++ b/include/linux/err.h
@@ -41,6 +41,8 @@ static inline void * __must_check ERR_PTR(long error)
return (void *) error;
}
+#define ERR_PTR_PCPU(ptr) ({ (void __percpu *)(unsigned long)ERR_PTR(ptr); })
+
/**
* PTR_ERR - Extract the error code from an error pointer.
* @ptr: An error pointer.
@@ -51,6 +53,8 @@ static inline long __must_check PTR_ERR(__force const void *ptr)
return (long) ptr;
}
+#define PTR_ERR_PCPU(ptr) ({ PTR_ERR((void *)(__force unsigned long)ptr); })
+
/**
* IS_ERR - Detect an error pointer.
* @ptr: The pointer to check.
@@ -61,6 +65,8 @@ static inline bool __must_check IS_ERR(__force const void *ptr)
return IS_ERR_VALUE((unsigned long)ptr);
}
+#define IS_ERR_PCPU(ptr) ({ IS_ERR((void *)(__force unsigned long)ptr); })
+
/**
* IS_ERR_OR_NULL - Detect an error pointer or a null pointer.
* @ptr: The pointer to check.
prev parent reply other threads:[~2024-08-18 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 15:26 Uros Bizjak
2024-08-18 19:51 ` Uros Bizjak [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='CAFULd4aFsoLxs57W6EfddcvZiy=oQ7SMVhSCkvNcPXDvXy6h+Q@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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