From: Dennis Zhou <dennis@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-mm@kvack.org, Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@gentwo.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm/percpu: Add a simple double-free check for per-CPU memory
Date: Thu, 4 Sep 2025 16:49:38 -0700 [thread overview]
Message-ID: <aLolklCw7wFbXrSl@palisades.local> (raw)
In-Reply-To: <20250904143514.Yk6Ap-jy@linutronix.de>
Hello,
On Thu, Sep 04, 2025 at 04:35:14PM +0200, Sebastian Andrzej Siewior wrote:
> The free path clears the allocation bits in pcpu_chunk::alloc_map. A
> simple double free check would be to check if the bits, which are about
> to be cleared, are already cleared.
>
I thought about the double free issue in the past. It's a bit imperfect
because the same pointer is handed out with no metadata for future
allocations. Worse, the whole percpu chunk could go away too should you
be so unlucky and then the whole path to get to the chunk goes awry.
> Check if the bit is already cleared. Issue a warning and abort free in
> that case.
>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
>
> I managed accidentally a double free recently. This would have noticed
> it. It looks low overhead so there might be no need to hide it behind a
> debug switch.
>
> mm/percpu.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/mm/percpu.c b/mm/percpu.c
> index d9cbaee92b605..a2abddd85294a 100644
> --- a/mm/percpu.c
> +++ b/mm/percpu.c
> @@ -1276,7 +1276,7 @@ static int pcpu_alloc_area(struct pcpu_chunk *chunk, int alloc_bits,
> static int pcpu_free_area(struct pcpu_chunk *chunk, int off)
> {
> struct pcpu_block_md *chunk_md = &chunk->chunk_md;
> - int bit_off, bits, end, oslot, freed;
> + int bit_off, bits, end, oslot, freed, free_bit;
>
> lockdep_assert_held(&pcpu_lock);
> pcpu_stats_area_dealloc(chunk);
> @@ -1289,6 +1289,11 @@ static int pcpu_free_area(struct pcpu_chunk *chunk, int off)
> end = find_next_bit(chunk->bound_map, pcpu_chunk_map_bits(chunk),
> bit_off + 1);
> bits = end - bit_off;
> +
> + free_bit = find_next_bit(chunk->alloc_map, end, bit_off);
> + if (WARN(free_bit != bit_off, "Trying to free already free memory"))
> + return 0;
> +
We might want to test_bit(bit_off, chunk->bound_map) also to make sure
we aren't accidentally doing partial frees if the region becomes say the
second half of a larger allocation before the double free.
Possibly good to move the WARN to free_percpu() and exit early too for
the other hooks rather than do all that with free size of 0.
> bitmap_clear(chunk->alloc_map, bit_off, bits);
>
> freed = bits * PCPU_MIN_ALLOC_SIZE;
> --
> 2.51.0
>
Thanks,
Dennis
prev parent reply other threads:[~2025-09-04 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 14:35 Sebastian Andrzej Siewior
2025-09-04 22:51 ` Andrew Morton
2025-09-05 17:14 ` Christoph Lameter (Ampere)
2025-09-04 23:49 ` Dennis Zhou [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=aLolklCw7wFbXrSl@palisades.local \
--to=dennis@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=cl@gentwo.org \
--cc=linux-mm@kvack.org \
--cc=tj@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