* [PATCH linux-next] ext4: use kcalloc instead of open coded arithmetic
@ 2023-12-15 13:43 yang.guang5
0 siblings, 0 replies; only message in thread
From: yang.guang5 @ 2023-12-15 13:43 UTC (permalink / raw)
To: tytso
Cc: jiang.xuexin, chen.haonan2, cgel.zte, adilger.kernel, linux-ext4,
linux-kernel
From: Yang Guang <yang.guang5@zte.com.cn>
Dynamic size calculations (especially multiplication) should not be
performed in memory allocator (or similar) function arguments due
to the risk of them overflowing. This could lead to values wrapping
around and a smaller allocation being made than the caller was
expecting. Using those allocations could lead to linear overflows
of heap memory and other misbehaviors.
So, use the purpose specific kcalloc() function instead of the argument
size * count in the kzalloc() function.
Signed-off-by: Chen Haonan <chen.haonan2@zte.com.cn>
---
fs/ext4/hash.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ext4/hash.c b/fs/ext4/hash.c
index deabe29da7fb..7a9afac1597c 100644
--- a/fs/ext4/hash.c
+++ b/fs/ext4/hash.c
@@ -302,7 +302,7 @@ int ext4fs_dirhash(const struct inode *dir, const char *name, int len,
if (len && IS_CASEFOLDED(dir) &&
(!IS_ENCRYPTED(dir) || fscrypt_has_encryption_key(dir))) {
- buff = kzalloc(sizeof(char) * PATH_MAX, GFP_KERNEL);
+ buff = kcalloc(PATH_MAX, sizeof(char), GFP_KERNEL);
if (!buff)
return -ENOMEM;
--
2.25.1
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2023-12-15 13:53 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-12-15 13:43 [PATCH linux-next] ext4: use kcalloc instead of open coded arithmetic yang.guang5
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox