From: Alan Huang <mmpgouride@gmail.com>
To: Liao Yuanhong <liaoyuanhong@vivo.com>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
"open list:BCACHEFS" <linux-bcachefs@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] bcachefs: Using vmalloc_array() for array space allocation
Date: Mon, 11 Aug 2025 20:50:37 +0800 [thread overview]
Message-ID: <1EB1AD1A-C14A-4A1F-A97B-55F956D241E7@gmail.com> (raw)
In-Reply-To: <20250811120953.529864-2-liaoyuanhong@vivo.com>
On Aug 11, 2025, at 20:09, Liao Yuanhong <liaoyuanhong@vivo.com> wrote:
>
> Replace kmalloc(size * sizeof) with kmalloc_array() for safer memory
> allocation and overflow prevention.
>
> Signed-off-by: Liao Yuanhong <liaoyuanhong@vivo.com>
> ---
> fs/bcachefs/btree_key_cache.c | 2 +-
> fs/bcachefs/btree_trans_commit.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/bcachefs/btree_key_cache.c b/fs/bcachefs/btree_key_cache.c
> index 4890cbc88e7c..8dd70024e513 100644
> --- a/fs/bcachefs/btree_key_cache.c
> +++ b/fs/bcachefs/btree_key_cache.c
> @@ -136,7 +136,7 @@ static struct bkey_cached *__bkey_cached_alloc(unsigned key_u64s, gfp_t gfp)
> struct bkey_cached *ck = kmem_cache_zalloc(bch2_key_cache, gfp);
> if (unlikely(!ck))
> return NULL;
> - ck->k = kmalloc(key_u64s * sizeof(u64), gfp);
> + ck->k = kmalloc_array(key_u64s, sizeof(u64), gfp);
> if (unlikely(!ck->k)) {
> kmem_cache_free(bch2_key_cache, ck);
> return NULL;
> diff --git a/fs/bcachefs/btree_trans_commit.c b/fs/bcachefs/btree_trans_commit.c
> index 4d58bdb233e9..4102a3cb2410 100644
> --- a/fs/bcachefs/btree_trans_commit.c
> +++ b/fs/bcachefs/btree_trans_commit.c
> @@ -396,7 +396,7 @@ btree_key_can_insert_cached_slowpath(struct btree_trans *trans, unsigned flags,
> bch2_trans_unlock_updates_write(trans);
> bch2_trans_unlock(trans);
>
> - new_k = kmalloc(new_u64s * sizeof(u64), GFP_KERNEL);
> + new_k = kmalloc_array(new_u64s, sizeof(u64), GFP_KERNEL);
No, it’s not an array.
> if (!new_k) {
> struct bch_fs *c = trans->c;
> bch_err(c, "error allocating memory for key cache key, btree %s u64s %u",
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2025-08-11 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 12:09 [PATCH 0/2] Cleanups and safer memory allocations Liao Yuanhong
2025-08-11 12:09 ` [PATCH 1/2] bcachefs: Using vmalloc_array() for array space allocation Liao Yuanhong
2025-08-11 12:50 ` Alan Huang [this message]
2025-08-11 13:02 ` Liao Yuanhong
2025-08-11 12:09 ` [PATCH 2/2] bcachefs: Remove redundant semicolons Liao Yuanhong
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=1EB1AD1A-C14A-4A1F-A97B-55F956D241E7@gmail.com \
--to=mmpgouride@gmail.com \
--cc=kent.overstreet@linux.dev \
--cc=liaoyuanhong@vivo.com \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®