From: Danilo Krummrich <dakr@kernel.org>
To: akpm@linux-foundation.org
Cc: cl@linux.com, penberg@kernel.org, rientjes@google.com,
iamjoonsoo.kim@lge.com, vbabka@suse.cz, roman.gushchin@linux.dev,
42.hyeyoo@gmail.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v2 1/2] mm: krealloc: consider spare memory for __GFP_ZERO
Date: Tue, 20 Aug 2024 01:23:00 +0200 [thread overview]
Message-ID: <65fd31b2-51c1-458c-a3fa-fadbde5039fb@kernel.org> (raw)
In-Reply-To: <20240812223707.32049-1-dakr@kernel.org>
On 8/13/24 12:34 AM, Danilo Krummrich wrote:
Gentle reminder on this one.
> As long as krealloc() is called with __GFP_ZERO consistently, starting
> with the initial memory allocation, __GFP_ZERO should be fully honored.
>
> However, if for an existing allocation krealloc() is called with a
> decreased size, it is not ensured that the spare portion the allocation
> is zeroed. Thus, if krealloc() is subsequently called with a larger size
> again, __GFP_ZERO can't be fully honored, since we don't know the
> previous size, but only the bucket size.
>
> Example:
>
> buf = kzalloc(64, GFP_KERNEL);
> memset(buf, 0xff, 64);
>
> buf = krealloc(buf, 48, GFP_KERNEL | __GFP_ZERO);
>
> /* After this call the last 16 bytes are still 0xff. */
> buf = krealloc(buf, 64, GFP_KERNEL | __GFP_ZERO);
>
> Fix this, by explicitly setting spare memory to zero, when shrinking an
> allocation with __GFP_ZERO flag set or init_on_alloc enabled.
>
> Acked-by: Vlastimil Babka <vbabka@suse.cz>
> Signed-off-by: Danilo Krummrich <dakr@kernel.org>
I think I forgot to add:
Cc: stable@vger.kernel.org
Not sure if there is a useful commit for "Fixes" though. AFAICT, this has been
broken since forever.
> ---
> mm/slab_common.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/mm/slab_common.c b/mm/slab_common.c
> index 40b582a014b8..cff602cedf8e 100644
> --- a/mm/slab_common.c
> +++ b/mm/slab_common.c
> @@ -1273,6 +1273,13 @@ __do_krealloc(const void *p, size_t new_size, gfp_t flags)
>
> /* If the object still fits, repoison it precisely. */
> if (ks >= new_size) {
> + /* Zero out spare memory. */
> + if (want_init_on_alloc(flags)) {
> + kasan_disable_current();
> + memset((void *)p + new_size, 0, ks - new_size);
> + kasan_enable_current();
> + }
> +
> p = kasan_krealloc((void *)p, new_size, flags);
> return (void *)p;
> }
>
> base-commit: b8dbbb7fe1db26c450a9d2c3302013154b3431df
prev parent reply other threads:[~2024-08-19 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 22:34 Danilo Krummrich
2024-08-12 22:34 ` [PATCH v2 2/2] mm: krealloc: clarify valid usage of __GFP_ZERO Danilo Krummrich
2024-08-13 2:32 ` David Rientjes
2024-08-13 2:32 ` [PATCH v2 1/2] mm: krealloc: consider spare memory for __GFP_ZERO David Rientjes
2024-08-19 23:23 ` Danilo Krummrich [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=65fd31b2-51c1-458c-a3fa-fadbde5039fb@kernel.org \
--to=dakr@kernel.org \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
/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