From: Charan Teja Kalla <quic_charante@quicinc.com>
To: Waiman Long <longman@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: Prevent derefencing NULL ptr in pfn_section_valid()
Date: Mon, 1 Jul 2024 19:20:21 +0530 [thread overview]
Message-ID: <bf0d9278-2b57-079e-cca5-21163e187ea3@quicinc.com> (raw)
In-Reply-To: <20240626001639.1350646-1-longman@redhat.com>
Hi Waiman,
On 6/26/2024 5:46 AM, Waiman Long wrote:
> Commit 5ec8e8ea8b77 ("mm/sparsemem: fix race in accessing
> memory_section->usage") changed pfn_section_valid() to add a READ_ONCE()
> call around "ms->usage" to fix a race with section_deactivate() where
> ms->usage can be cleared. The READ_ONCE() call, by itself, is not enough
> to prevent NULL pointer dereference. We need to check its value before
> dereferencing it.
I am unable to see a scenario where ms->usage will be NULL when
pfn_section_valid() is called:
1) In pfn_valid, valid_section() check ensures that pfn_section_valid()
is not called as the section is marked as invalid.
2) In pfn_to_online_page, online_section() check ensures that
pfn_section_valid() is not called.
and in the update path, we do:
kfree_rcu(ms->usage, rcu);
WRITE_ONCE(ms->usage, NULL);
Could you help me in understanding about what I am missing here, please?
>
> Fixes: 5ec8e8ea8b77 ("mm/sparsemem: fix race in accessing memory_section->usage")
> Signed-off-by: Waiman Long <longman@redhat.com>
> ---
> include/linux/mmzone.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
> index 8f9c9590a42c..b1dcf6ddb406 100644
> --- a/include/linux/mmzone.h
> +++ b/include/linux/mmzone.h
> @@ -1980,8 +1980,9 @@ static inline int subsection_map_index(unsigned long pfn)
> static inline int pfn_section_valid(struct mem_section *ms, unsigned long pfn)
> {
> int idx = subsection_map_index(pfn);
> + struct mem_section_usage *usage = READ_ONCE(ms->usage);
>
> - return test_bit(idx, READ_ONCE(ms->usage)->subsection_map);
> + return usage ? test_bit(idx, usage->subsection_map) : 0;
> }
> #else
> static inline int pfn_section_valid(struct mem_section *ms, unsigned long pfn)
next prev parent reply other threads:[~2024-07-01 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 0:16 Waiman Long
2024-07-01 13:50 ` Charan Teja Kalla [this message]
2024-07-02 23:45 ` Waiman Long
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=bf0d9278-2b57-079e-cca5-21163e187ea3@quicinc.com \
--to=quic_charante@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox