From: Baoquan He <bhe@redhat.com>
To: Vlad Dumitrescu <vdumitrescu@nvidia.com>
Cc: Dennis Zhou <dennis@kernel.org>, Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@gentwo.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] percpu: fix race on alloc failed warning limit
Date: Sun, 24 Aug 2025 11:07:34 +0800 [thread overview]
Message-ID: <aKqB9sGmgJwsTXGg@MiWiFi-R3L-srv> (raw)
In-Reply-To: <ab22061a-a62f-4429-945b-744e5cc4ba35@nvidia.com>
On 08/22/25 at 03:55pm, Vlad Dumitrescu wrote:
> The 'allocation failed, ...' warning messages can cause unlimited log
> spam, contrary to the implementation's intent.
>
> The warn_limit variable is accessed without synchronization. If more
> than <warn_limit> threads enter the warning path at the same time, the
> variable will get decremented past 0. Once it becomes negative, the
> non-zero check will always return true leading to unlimited log spam.
>
> Use atomic operations to access warn_limit and change the check to test
> for positive (> 0) as it can still become negative.
>
> While the change cited in Fixes is only adjacent, the warning limit
> implementation was correct before it. Only non-atomic allocations were
> considered for warnings, and those happened to hold pcpu_alloc_mutex
> while accessing warn_limit.
>
> Fixes: f7d77dfc91f7 ("mm/percpu.c: print error message too if atomic alloc failed")
> Signed-off-by: Vlad Dumitrescu <vdumitrescu@nvidia.com>
> ---
> mm/percpu.c | 20 ++++++++++++--------
> 1 file changed, 12 insertions(+), 8 deletions(-)
>
> diff --git a/mm/percpu.c b/mm/percpu.c
> index a56f35dcc417..c1a4089eb4c3 100644
> --- a/mm/percpu.c
> +++ b/mm/percpu.c
> @@ -1734,7 +1734,7 @@ void __percpu *pcpu_alloc_noprof(size_t size, size_t align, bool reserved,
> bool is_atomic;
> bool do_warn;
> struct obj_cgroup *objcg = NULL;
> - static int warn_limit = 10;
> + static atomic_t warn_limit = ATOMIC_INIT(10);
> struct pcpu_chunk *chunk, *next;
> const char *err;
> int slot, off, cpu, ret;
> @@ -1904,13 +1904,17 @@ void __percpu *pcpu_alloc_noprof(size_t size, size_t align, bool reserved,
> fail:
> trace_percpu_alloc_percpu_fail(reserved, is_atomic, size, align);
>
> - if (do_warn && warn_limit) {
> - pr_warn("allocation failed, size=%zu align=%zu atomic=%d, %s\n",
> - size, align, is_atomic, err);
> - if (!is_atomic)
> - dump_stack();
> - if (!--warn_limit)
> - pr_info("limit reached, disable warning\n");
> + if (do_warn && atomic_read(&warn_limit) > 0) {
> + int remaining = atomic_dec_return(&warn_limit);
> +
> + if (remaining >= 0) {
> + pr_warn("allocation failed, size=%zu align=%zu atomic=%d, %s\n",
> + size, align, is_atomic, err);
> + if (!is_atomic)
> + dump_stack();
> + if (remaining == 0)
> + pr_info("limit reached, disable warning\n");
> + }
A good catch, and the new code logic makes code more robust, thanks for
the fix.
Reviewed-by: Baoquan He <bhe@redhat.com>
> }
>
> if (is_atomic) {
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-08-24 3:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 22:55 [PATCH] percpu: fix race on alloc failed warning limit Vlad Dumitrescu
2025-08-24 3:07 ` Baoquan He [this message]
2025-09-02 17:39 ` Christoph Lameter (Ampere)
2025-09-02 21:06 ` Vlad Dumitrescu
2025-09-02 21:41 ` Christoph Lameter (Ampere)
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=aKqB9sGmgJwsTXGg@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=dennis@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tj@kernel.org \
--cc=vdumitrescu@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.