From: Vlastimil Babka <vbabka@suse.cz>
To: Oscar Salvador <osalvador@suse.de>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Michal Hocko <mhocko@suse.com>, Marco Elver <elver@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Alexander Potapenko <glider@google.com>,
kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH 1/2] mm,page_owner: Check for null stack_record before bumping its refcount
Date: Fri, 8 Mar 2024 08:53:05 +0100 [thread overview]
Message-ID: <d6d8aef5-9ebf-4a38-bdb5-f1daf7818873@suse.cz> (raw)
In-Reply-To: <20240306123217.29774-2-osalvador@suse.de>
On 3/6/24 13:32, Oscar Salvador wrote:
> Although the retrieval of the stack_records for {dummy,failure}_handle
> happen when page_owner gets initialized, there seems to be some situations
> where stackdepot space has been already depleted by then, so we get
> 0-handles which make stack_records being NULL for those cases.
>
> Be careful to 1) only bump stack_records refcount and 2) only access
> stack_record fields if we actually have a non-null stack_record between
> hands.
>
> Reported-by: kernel test robot <oliver.sang@intel.com>
> Closes: https://lore.kernel.org/oe-lkp/202403051032.e2f865a-lkp@intel.com
> Fixes: 4bedfb314bdd ("mm,page_owner: implement the tracking of the stacks count")
> Signed-off-by: Oscar Salvador <osalvador@suse.de>
Reviewed-by: Vlastimil Babka <vbabka@suse.cz>
> ---
> mm/page_owner.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/mm/page_owner.c b/mm/page_owner.c
> index 033e349f6479..7163a1c44ccf 100644
> --- a/mm/page_owner.c
> +++ b/mm/page_owner.c
> @@ -107,8 +107,10 @@ static __init void init_page_owner(void)
> /* Initialize dummy and failure stacks and link them to stack_list */
> dummy_stack.stack_record = __stack_depot_get_stack_record(dummy_handle);
> failure_stack.stack_record = __stack_depot_get_stack_record(failure_handle);
> - refcount_set(&dummy_stack.stack_record->count, 1);
> - refcount_set(&failure_stack.stack_record->count, 1);
> + if (dummy_stack.stack_record)
> + refcount_set(&dummy_stack.stack_record->count, 1);
> + if (failure_stack.stack_record)
> + refcount_set(&failure_stack.stack_record->count, 1);
> dummy_stack.next = &failure_stack;
> stack_list = &dummy_stack;
> }
> @@ -856,6 +858,9 @@ static int stack_print(struct seq_file *m, void *v)
> unsigned long nr_entries;
> struct stack_record *stack_record = stack->stack_record;
>
> + if (!stack->stack_record)
> + return 0;
> +
> nr_entries = stack_record->size;
> entries = stack_record->entries;
> stack_count = refcount_read(&stack_record->count) - 1;
next prev parent reply other threads:[~2024-03-08 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 12:32 [PATCH 0/2] page_owner: Fixup and cleanup Oscar Salvador
2024-03-06 12:32 ` [PATCH 1/2] mm,page_owner: Check for null stack_record before bumping its refcount Oscar Salvador
2024-03-08 7:53 ` Vlastimil Babka [this message]
2024-03-06 12:32 ` [PATCH 2/2] mm,page_owner: Drop unnecesary check Oscar Salvador
2024-03-08 7:53 ` Vlastimil Babka
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=d6d8aef5-9ebf-4a38-bdb5-f1daf7818873@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=oliver.sang@intel.com \
--cc=osalvador@suse.de \
/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®