From: David Hildenbrand <david@redhat.com>
To: Zi Yan <ziy@nvidia.com>, Antonio Quartulli <antonio@mandelbit.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Nico Pache <npache@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>,
Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [RFC] mm/huge_memory: prevent potential NULL pointer dereference
Date: Wed, 16 Jul 2025 17:18:03 +0200 [thread overview]
Message-ID: <955c523e-9eea-48fb-a604-9ec445e563f4@redhat.com> (raw)
In-Reply-To: <FDB41C5A-5C1B-426D-900B-AE7A1DE78CB2@nvidia.com>
On 16.07.25 17:10, Zi Yan wrote:
> On 16 Jul 2025, at 10:58, Antonio Quartulli wrote:
>
>> I just found this issue in the last linux-next Coverity report and it
>> caught my attention.
>> I am not familiar with this code, therefore I am sending this patch
>> as RFC because I am not 100% sure whether this is a false positive or
>> not.
>> However, it seems potentially legit to me:
>>
>> In __folio_split(), when looping over folios we dereference
>> `mapping` before ensuring it is non-NULL.
>>
>> Following code in the loop body performs such check, thus
>> suggesting that `mapping` may be NULL and accessing it
>> without any check may be dangerous.
>>
>> Add NULL check before passing it to shmem_mapping().
>>
>> Cc: Zi Yan <ziy@nvidia.com>
>> Fixes: 00527733d0dc ("mm/huge_memory: add two new (not yet used) functions for folio_split()")
>> Addresses-Coverity-ID: 1647614 ("FORWARD_NULL")
>> Signed-off-by: Antonio Quartulli <antonio@mandelbit.com>
>> ---
>> mm/huge_memory.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
>> index 389620c65a5f..d649026db95a 100644
>> --- a/mm/huge_memory.c
>> +++ b/mm/huge_memory.c
>> @@ -3802,7 +3802,7 @@ static int __folio_split(struct folio *folio, unsigned int new_order,
>>
>> /* Some pages can be beyond EOF: drop them from cache */
>> if (new_folio->index >= end) {
>> - if (shmem_mapping(mapping))
>> + if (mapping && shmem_mapping(mapping))
>> nr_shmem_dropped += folio_nr_pages(new_folio);
>> else if (folio_test_clear_dirty(new_folio))
>> folio_account_cleaned(
> Hi Antonio,
>
> Is there a way of preventing Coverity/sparse from checking certain code?
> This non-NULL mapping issue pops up every time I touch the code.
Probably we could make that code more readable and achieve it:
diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index 24aff14d22a1e..acf56aae1a2ef 100644
--- a/mm/huge_memory.c
+++ b/mm/huge_memory.c
@@ -3775,6 +3775,7 @@ static int __folio_split(struct folio *folio, unsigned int new_order,
*/
for (new_folio = folio_next(folio); new_folio != next_folio;
new_folio = next) {
+ unsigned long nr_pages = folio_nr_pages(new_folio);
next = folio_next(new_folio);
expected_refs = folio_expected_ref_count(new_folio) + 1;
@@ -3782,20 +3783,20 @@ static int __folio_split(struct folio *folio, unsigned int new_order,
lru_add_split_folio(folio, new_folio, lruvec, list);
- /* Some pages can be beyond EOF: drop them from cache */
- if (new_folio->index >= end) {
- if (shmem_mapping(mapping))
- nr_shmem_dropped += folio_nr_pages(new_folio);
- else if (folio_test_clear_dirty(new_folio))
- folio_account_cleaned(
- new_folio,
- inode_to_wb(mapping->host));
- __filemap_remove_folio(new_folio, NULL);
- folio_put_refs(new_folio,
- folio_nr_pages(new_folio));
- } else if (mapping) {
- __xa_store(&mapping->i_pages, new_folio->index,
- new_folio, 0);
+ /* Add the new folio to the page cache ... */
+ if (mapping) {
+ /* ... however, drop folios beyond EOF. */
+ if (new_folio->index >= end) {
+ if (shmem_mapping(mapping))
+ nr_shmem_dropped += nr_pages;
+ else if (folio_test_clear_dirty(new_folio))
+ folio_account_cleaned(new_folio, inode_to_wb(mapping->host));
+ __filemap_remove_folio(new_folio, NULL);
+ folio_put_refs(new_folio, nr_pages);
+ } else {
+ __xa_store(&mapping->i_pages,
+ new_folio->index, new_folio, 0);
+ }
} else if (swap_cache) {
__xa_store(&swap_cache->i_pages,
swap_cache_index(new_folio->swap),
Having that logic in a helper would be cleaner, but not straight-forward due
to things like nr_shmem_dropped.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-07-16 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 14:58 [RFC] mm/huge_memory: prevent potential NULL pointer dereference Antonio Quartulli
2025-07-16 15:07 ` Lorenzo Stoakes
2025-07-16 19:05 ` Antonio Quartulli
2025-07-16 19:10 ` Lorenzo Stoakes
2025-07-16 19:13 ` Antonio Quartulli
2025-07-16 15:10 ` Zi Yan
2025-07-16 15:18 ` David Hildenbrand [this message]
2025-07-16 15:24 ` Zi Yan
2025-07-16 15:31 ` David Hildenbrand
2025-07-16 16:18 ` Dan Carpenter
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=955c523e-9eea-48fb-a604-9ec445e563f4@redhat.com \
--to=david@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=antonio@mandelbit.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dan.carpenter@linaro.org \
--cc=dev.jain@arm.com \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=ziy@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.