From: Vlastimil Babka <vbabka@suse.cz>
To: Harry Yoo <harry.yoo@oracle.com>, Ye Bin <yebin@huaweicloud.com>
Cc: cl@linux.com, penberg@kernel.org, rientjes@google.com,
iamjoonsoo.kim@lge.com, akpm@linux-foundation.org,
roman.gushchin@linux.dev, linux-mm@kvack.org, yebin10@huawei.com
Subject: Re: [PATCH] mm/slab: call __kmalloc_noprof() when size isn't builtin constant in kmalloc_array_noprof()
Date: Tue, 4 Mar 2025 11:03:54 +0100 [thread overview]
Message-ID: <bc87e423-7173-4c70-8747-8472d7e36d8b@suse.cz> (raw)
In-Reply-To: <Z8RdfF8hnIBB3hEO@harry>
On 3/2/25 14:30, Harry Yoo wrote:
> On Sat, Mar 01, 2025 at 04:37:20PM +0800, Ye Bin wrote:
>> From: Ye Bin <yebin10@huawei.com>
>>
>> If 'n' or 'size' isn't builtin constant just call __kmalloc_noprof()
>> in kmalloc_array_noprof().
>>
>> Fixes: 7bd230a26648 ("mm/slab: enable slab allocation tagging for kmalloc and friends")
>> Signed-off-by: Ye Bin <yebin10@huawei.com>
>> ---
>> include/linux/slab.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/include/linux/slab.h b/include/linux/slab.h
>> index 3b03b31831a9..0edb8363fc4f 100644
>> --- a/include/linux/slab.h
>> +++ b/include/linux/slab.h
>> @@ -947,7 +947,7 @@ static inline __alloc_size(1, 2) void *kmalloc_array_noprof(size_t n, size_t siz
>> return NULL;
>> if (__builtin_constant_p(n) && __builtin_constant_p(size))
>> return kmalloc_noprof(bytes, flags);
>> - return kmalloc_noprof(bytes, flags);
>> + return __kmalloc_noprof(bytes, flags);
>
> Can we simply call kmalloc_noprof(bytes, flags) once instead?
>
> The compiler should know 'bytes' is a constant if both 'n' and 'size' are
> constants.
Right, applied like this, hope it's ok?
commit a6553ee4b00ba4b1466a81fb00fa4679b7ce5339 (HEAD -> slab/for-6.15/fixes-cleanups)
Author: Ye Bin <yebin10@huawei.com>
Date: Sat Mar 1 16:37:20 2025 +0800
mm/slab: call kmalloc_noprof() unconditionally in kmalloc_array_noprof()
If 'n' or 'size' isn't builtin constant, we used to call __kmalloc()
before commit 7bd230a26648 ("mm/slab: enable slab allocation tagging for
kmalloc and friends"), which inadvertedly changed both paths to
kmalloc_noprof().
As Harry Yoo points out we can just call kmalloc_noprof()
unconditionally. If the compiler knows n and size are constants it
doesn't guarantee that bytes will be also seen as constant, and that is
the important test in kmalloc_noprof() here, so we can just defer to it
always.
[ vbabka@suse.cz: change as Harry suggested and adjust commit log ]
Fixes: 7bd230a26648 ("mm/slab: enable slab allocation tagging for kmalloc and friends")
Signed-off-by: Ye Bin <yebin10@huawei.com>
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
diff --git a/include/linux/slab.h b/include/linux/slab.h
index 09eedaecf120..ab05a143d09a 100644
--- a/include/linux/slab.h
+++ b/include/linux/slab.h
@@ -941,8 +941,6 @@ static inline __alloc_size(1, 2) void *kmalloc_array_noprof(size_t n, size_t siz
if (unlikely(check_mul_overflow(n, size, &bytes)))
return NULL;
- if (__builtin_constant_p(n) && __builtin_constant_p(size))
- return kmalloc_noprof(bytes, flags);
return kmalloc_noprof(bytes, flags);
}
#define kmalloc_array(...) alloc_hooks(kmalloc_array_noprof(__VA_ARGS__))
next prev parent reply other threads:[~2025-03-04 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 8:37 Ye Bin
2025-03-02 13:30 ` Harry Yoo
2025-03-04 10:03 ` Vlastimil Babka [this message]
2025-03-04 23:32 ` Harry Yoo
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=bc87e423-7173-4c70-8747-8472d7e36d8b@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=harry.yoo@oracle.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=yebin10@huawei.com \
--cc=yebin@huaweicloud.com \
/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