From: Lance Yang <lance.yang@linux.dev>
To: ngocthang2710.1999@gmail.com
Cc: akpm@linux-foundation.org, david@kernel.org, ljs@kernel.org,
ziy@nvidia.com, baolin.wang@linux.alibaba.com,
liam@infradead.org, nico.pache@linux.dev, ryan.roberts@arm.com,
dev.jain@arm.com, baohua@kernel.org, usama.arif@linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] khugepaged: hold invalidate_lock across collapse_file() readahead
Date: Mon, 14 Sep 2026 00:16:58 +0800 [thread overview]
Message-ID: <dc6f3b89-58cf-48c6-bb4f-9fe605c92028@linux.dev> (raw)
In-Reply-To: <20260913161245.11120-1-lance.yang@linux.dev>
On 2026/9/14 00:12, Lance Yang wrote:
> Hi Nguyen,
>
> Good catch, thanks!
>
> On Sun, Sep 13, 2026 at 05:11:42PM +0700, Nguyen Ngoc Thang wrote:
>> collapse_file() calls page_cache_sync_readahead() to fault in missing
>> pages before collapsing them into a THP. That helper takes
>> mapping->invalidate_lock itself for the duration of the call, then
>> drops it -- but truncate (e.g. ext4_setattr() -> truncate_pagecache())
>> takes invalidate_lock and then waits on each page's folio lock while
>> holding it. If collapse_file() has already locked one of those folios
>> by the time truncate reaches it, and then tries to acquire
>> invalidate_lock again (e.g. on the next iteration, or via a nested
>> readahead call), the two paths can deadlock/hang on each other's lock:
>> truncate blocked on the folio lock collapse holds, and collapse
>> blocked waiting for invalidate_lock that truncate holds.
>
> That can happen on the first readahead call.
>
>>
>> Reproducing this over ~150,000 collapse iterations with truncate
>> racing concurrently reliably hits hung_task: blocked tasks within
>> about 20 seconds on an unpatched kernel.
>>
>> Fix it by taking invalidate_lock_shared once for the whole scan, before
>> locking any folio, and using page_cache_ra_unbounded() directly in the
>> readahead call site instead of page_cache_sync_readahead(), since the
>> latter would try to retake the lock we already hold.
>> page_cache_ra_unbounded() does not clamp to EOF like the helper it
>> replaces, so clamp the requested range explicitly.
>>
>> Reported-by: syzbot+16bf7cd0ebeb1de93aa5@syzkaller.appspotmail.com
>> Closes: https://syzkaller.appspot.com/bug?extid=16bf7cd0ebeb1de93aa5
>
> Ouch, we should add a Fixes tag and Cc stable:
>
> Fixes: 730633f0b7f9 ("mm: Protect operations adding pages to page cache with invalidate_lock")
> Cc: stable@vger.kernel.org
>
> 730633f0b7f9 added invalidate_lock acquisition to readahead but missed
> collapse_file(), which already called it with page locks held. The
> subsequent filesystem conversions made the deadlock possible by taking
> invalidate_lock before locking pages :( right?
>
>> Signed-off-by: Nguyen Ngoc Thang <ngocthang2710.1999@gmail.com>
>> ---
Forgot to mention:
I reproduced the hang too, and it goes away with this patch applied :)
Tested-by: Lance Yang <lance.yang@linux.dev>
>> mm/khugepaged.c | 25 ++++++++++++++++++++++---
>> 1 file changed, 22 insertions(+), 3 deletions(-)
>>
>> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
>> index 11ff98d55c76..690ccbcdf593 100644
>> --- a/mm/khugepaged.c
>> +++ b/mm/khugepaged.c
>> @@ -2267,6 +2267,13 @@ static enum scan_result collapse_file(struct mm_struct *mm, unsigned long addr,
>> VM_WARN_ON_ONCE(!is_shmem && !mapping_pmd_folio_support(mapping));
>> VM_WARN_ON_ONCE(start & (HPAGE_PMD_NR - 1));
>>
>> + /*
>> + * Take invalidate_lock before any folio lock: the readahead below
>> + * needs it, and truncate holds it while waiting on folio locks.
>> + */
>> + if (!is_shmem)
>> + filemap_invalidate_lock_shared(mapping);
>
> Could we take the lock after alloc_charge_folio() succeeds, before
> locking any folio? That would keep allocation and charging outside the
> critical section. And if allocation fails, we should skip the unlock :)
>
> Cheers, Lance
>
>> +
>> result = alloc_charge_folio(&new_folio, mm, cc, HPAGE_PMD_ORDER);
>> if (result != SCAN_SUCCEED)
>> goto out;
>> @@ -2337,10 +2344,20 @@ static enum scan_result collapse_file(struct mm_struct *mm, unsigned long addr,
>> }
>> } else { /* !is_shmem */
>> if (!folio || xa_is_value(folio)) {
>> + DEFINE_READAHEAD(ractl, file, &file->f_ra,
>> + mapping, index);
>> + pgoff_t eof = DIV_ROUND_UP(i_size_read(mapping->host),
>> + PAGE_SIZE);
>> +
>> xas_unlock_irq(&xas);
>> - page_cache_sync_readahead(mapping, &file->f_ra,
>> - file, index,
>> - end - index);
>> + /*
>> + * invalidate_lock held above; don't retake it.
>> + * page_cache_ra_unbounded(), unlike the readahead
>> + * helper this replaces, does not clamp to EOF.
>> + */
>> + if (index < eof)
>> + page_cache_ra_unbounded(&ractl,
>> + min(end, eof) - index, 0);
>> /* drain lru cache to help folio_isolate_lru() */
>> lru_add_drain();
>> folio = filemap_lock_folio(mapping, index);
>> @@ -2672,6 +2689,8 @@ static enum scan_result collapse_file(struct mm_struct *mm, unsigned long addr,
>> folio_unlock(new_folio);
>> folio_put(new_folio);
>> out:
>> + if (!is_shmem)
>> + filemap_invalidate_unlock_shared(mapping);
>> VM_BUG_ON(!list_empty(&pagelist));
>> trace_mm_khugepaged_collapse_file(mm, new_folio, index, addr, is_shmem, file, HPAGE_PMD_NR, result);
>> return result;
>> --
>> 2.43.0
>>
>>
next prev parent reply other threads:[~2026-09-13 16:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 10:11 Nguyen Ngoc Thang
2026-09-13 16:12 ` Lance Yang
2026-09-13 16:16 ` Lance Yang [this message]
2026-09-13 16:31 ` Zi Yan
2026-09-13 16:36 ` [PATCH v2] " Nguyen Ngoc Thang
2026-09-13 18:17 ` Andrew Morton
2026-09-13 18:48 ` Lorenzo Stoakes (ARM)
2026-09-13 18:49 ` Lorenzo Stoakes (ARM)
2026-09-14 14:19 ` David Hildenbrand (Arm)
2026-09-14 16:58 ` Mike Rapoport
2026-09-13 22:34 ` Matthew Wilcox
2026-09-14 3:14 ` Baolin Wang
2026-09-13 18:43 ` [PATCH] " Lorenzo Stoakes (ARM)
-- strict thread matches above, loose matches on Subject: below --
2026-09-13 10:08 Nguyen Ngoc Thang
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=dc6f3b89-58cf-48c6-bb4f-9fe605c92028@linux.dev \
--to=lance.yang@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=ngocthang2710.1999@gmail.com \
--cc=nico.pache@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=stable@vger.kernel.org \
--cc=usama.arif@linux.dev \
--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 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®