From: Vlastimil Babka <vbabka@suse.cz>
To: Brendan Jackman <jackmanb@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/page_alloc: Warn on nr_reserved_highatomic underflow
Date: Tue, 25 Feb 2025 19:51:21 +0100 [thread overview]
Message-ID: <b5324a7b-e235-485c-8a43-ee7ad8c098b3@suse.cz> (raw)
In-Reply-To: <20250225-warn-underflow-v1-1-3dc542941d3a@google.com>
On 2/25/25 19:45, Brendan Jackman wrote:
> As documented in the comment this underflow should not happen. The
> locking has indeed changed here since the comment was written, see the
> migratetype hygiene patches[0]. However, those changes made the locking
> _safer_, so the underflow _really_ shouldn't happen now. So upgrade
> the comment to a warning.
>
> [0] https://lore.kernel.org/all/20240320180429.678181-7-hannes@cmpxchg.org/T/#m3da87e6cc3348a4640aa298137bc9f8f61b76c84
>
> Signed-off-by: Brendan Jackman <jackmanb@google.com>
Reviewed-by: Vlastimil Babka <vbabka@suse.cz>
Thanks!
> ---
> mm/page_alloc.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 5d8e274c8b1d500d263a17ef36fe190f60b88196..715a9cfe162090cca9eb819a34c64f9a1c6db29a 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -3095,6 +3095,7 @@ static bool unreserve_highatomic_pageblock(const struct alloc_context *ac,
> if (!page)
> continue;
>
> + size = max(pageblock_nr_pages, 1UL << order);
> /*
> * It should never happen but changes to
> * locking could inadvertently allow a per-cpu
> @@ -3102,8 +3103,8 @@ static bool unreserve_highatomic_pageblock(const struct alloc_context *ac,
> * while unreserving so be safe and watch for
> * underflows.
> */
> - size = max(pageblock_nr_pages, 1UL << order);
> - size = min(size, zone->nr_reserved_highatomic);
> + if (WARN_ON_ONCE(size > zone->nr_reserved_highatomic))
> + size = zone->nr_reserved_highatomic;
> zone->nr_reserved_highatomic -= size;
>
> /*
>
> ---
> base-commit: 0c789105c9d6c65777c995f4935f2e119d5a31a5
> change-id: 20250225-warn-underflow-7ab0069182e2
>
> Best regards,
prev parent reply other threads:[~2025-02-25 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 18:45 Brendan Jackman
2025-02-25 18:51 ` Vlastimil Babka [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=b5324a7b-e235-485c-8a43-ee7ad8c098b3@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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